This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: MacOSX and Windows binaries
- From: FX Coudert <fxcoudert at gmail dot com>
- To: "fortran at gcc dot gnu dot org List" <fortran at gcc dot gnu dot org>
- Date: 2007年10月18日 00:10:52 +0100
- Subject: Re: MacOSX and Windows binaries
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:mime-version:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; bh=Eo/MP+1V7YMXCdbk0f+IjTQIKmsiWJhFZwiZg9YGWjo=; b=gQpfwFHH/mw7EcF6HGFn+Vml4oKVLtuXx6QbxuLDi+xYhUkhooX9chAae5jAqG8KwsP9aC+apg70lcLeKXEk29euCzqgYQXKSJdMqWJAJw3Bacb6fEOpV/rUaCUEnOkS23b5k/iv27QJbJGnOzzVwSfNuNHm6kf7dfeNVZ/yWQw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:mime-version:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; b=oJz1GKZLBWa+Jy+UY9f5QkegicKsXKrWA7QYG7DkfIzMwh7th8hNupRxAZxTBbgkQZ+fvabixfY9GOGps1tzBFP8buIuQZqoYbkPDGyL4n3UDGn4Q5+2c4+DW75UmeDNudyC5zRy8JcLfHPYwAj9gfdZlAWdb7zqXxC4ZoTEXAU=
- References: <CA2A0F47-7DD6-47C0-9858-6036EF7D0025@gmail.com>
Thanks for the MacOSX x86 build. Unfortunately there is a
regression in my full application that I haven't been able to
isolate into a test case. I get a nonsensical error message:
~/gfc/geloe$ gfortran -c readlens.f90
readlens.f90:407.103:
2','MODE SEQ','NAME '//trim(titles),'UNIT '//UpperCase(UNAME(kunit
(0))(:2))
1
Error: Variable 'str' is used at (1) before the ENTRY statement in
which it is a parameter
The is no variable 'str' in the statement pointed to. My
application continues to compile and execute fine with g95, ivf,
lf95 and xlf (including with full bounds and runtime
uninitialization checking).
Every time there is a new build of gfortran, I end up fighting at
least one thing that used to work but has been broken since the
last build.
Well, we do our best not to regress, but unfortunately mistakes do
creep in, that's why testing is so important. If you can open a bug
report for this problem, we'll get it fixed ASAP.
FX