This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch, gfortran] common blocks getting mangled in nested modules

From: Paul Thomas <paulthomas2 at wanadoo dot fr>
To: Richard E Maine <Richard dot Maine at nasa dot gov>
Cc: "'fortran at gcc dot gnu dot org'" <fortran at gcc dot gnu dot org>,patch <gcc-patches at gcc dot gnu dot org>,Tobias dot Schlueter at Physik dot Uni-Muenchen dot DE
Date: Fri, 19 Aug 2005 20:23:38 +0200
Subject: Re: [Patch, gfortran] common blocks getting mangled in nested modules
References: <1124396183.4304ec973d049@www.cip.physik.uni-muenchen.de> <43056D29.3020304@wanadoo.fr> <dcb2e5fb7ed3b778d4f24b4e905093b4@nasa.gov> <43061107.1010404@wanadoo.fr> <baf098c3f36e0d3bb274aadbb34c5e78@nasa.gov>

Richard,

> Yep. That's a fine example, which I claim is standard-conforming. FWIW, I tried it with both > NAG and in g95, as they were handy to me, and both worked fine on it

The standard says explicitly that it is OK or, rather, that it is not not OK.

Paul

References:
- Re: [Patch, gfortran] common blocks getting mangled in nested modules
  - From: Tobias . Schlueter
- Re: [Patch, gfortran] common blocks getting mangled in nested modules
  - From: Paul Thomas
- Re: [Patch, gfortran] common blocks getting mangled in nested modules
  - From: Richard E Maine
- Re: [Patch, gfortran] common blocks getting mangled in nested modules
  - From: Paul Thomas
- Re: [Patch, gfortran] common blocks getting mangled in nested modules
  - From: Richard E Maine

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]