This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [g95] - compiler crash on internal writes
- From: Thomas Koenig <Thomas dot Koenig at online dot de>
- To: Catherine Moroney <Catherine dot M dot Moroney at jpl dot nasa dot gov>
- Cc: fortran at gcc dot gnu dot org, Brian dot Rheingans at jpl dot nasa dot gov
- Date: Wed, 12 Jan 2005 19:58:56 +0100
- Subject: Re: [g95] - compiler crash on internal writes
- References: <41E56B08.86728D48@jpl.nasa.gov>
On Wed, Jan 12, 2005 at 10:23:04AM -0800, Catherine Moroney wrote:
> I have a question on whether g95 handles internal writes.
You have reached the mailing list for the gfortran project.
gfortran and g95 are two different projects. See
http://gfortran.org/index.php/Gfortran/TheOtherGccBasedF95Compiler
for an explanation.
> for instance: write(mystring,'(a,i3,a)') 'xxx',100,'yyy'
> will cause a compiler crash.
$ cat mystring.f90
character(len=50) mystring
write(mystring,'(a,i3,a)') 'xxx',100,'yyy'
print *,mystring
end
$ gfortran mystring.f90
$ ./a.out
xxx100yyy
$ gfortran -v
Using built-in specs.
Configured with: ../gcc/configure --prefix=/home/ig25 --enable-languages=c,c++,f95
Thread model: posix
gcc version 4.0.0 20050108 (experimental)
... which looks to be OK.
There is a known issue with gfortran if mystring is an array of
characters; this can be found at http://gcc.gnu.org/PR15966 .
> Is this a known problem with g95? Can you suggest a work-around
> for this?
gfortran bugs can be found at http://gcc.gnu.org/bugzilla or
from a side link at http://gfortran.org/.
Thomas