This is the mail archive of the gcc@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: Instability in successive builds of fortran mod files with f951

From: Janne Blomqvist <blomqvist dot janne at gmail dot com>
To: Ian Lance Taylor <iant at google dot com>
Cc: Simon Baldwin <simonb at google dot com>, gcc at gcc dot gnu dot org, fortran at gcc dot gnu dot org
Date: Fri, 5 Oct 2012 22:07:31 +0300
Subject: Re: Instability in successive builds of fortran mod files with f951
References: <CAPTY64qOU6SASGA-yH8-_Sos85_wWAgh8Rm=rERT=q20xp5Fzw@mail.gmail.com> <CAKOQZ8yVgZKeCZ40fdgVGXnQN-93=W9ZTX2WGYWPnOShN8Z7JQ@mail.gmail.com>

On Fri, Oct 5, 2012 at 9:53 PM, Ian Lance Taylor <iant@google.com> wrote:
> On Fri, Oct 5, 2012 at 10:45 AM, Simon Baldwin <simonb@google.com> wrote:
>>
>> I've looked at fortran/module.c and at libgomp/omp_lib.mod, and this
>> is not a bug.
>
> This isn't particularly helpful, but, based on the rest of your
> description, this is a bug.  The compiler should never depend on the
> order of pointer values.
>
> (Added fortran@gcc.gnu.org).
>
> Ian

Also known as PR 51727, FWIW. See also the ML thread referenced in the
PR (continued at http://gcc.gnu.org/ml/fortran/2012-01/msg00003.html).
So yes, it's a known problem, but so far nobody has found the time to
fix it.

-- 
Janne Blomqvist

References:
- Instability in successive builds of fortran mod files with f951
  - From: Simon Baldwin
- Re: Instability in successive builds of fortran mod files with f951
  - From: Ian Lance Taylor

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