[Bug fortran/38249] read(*,*) seems to have broken

2008-11-24 Thread jvdelisle at gcc dot gnu dot org
--- Comment #10 from jvdelisle at gcc dot gnu dot org 2008-11-25 02:18 --- We did at one time talk about innoculating libgfortran or some such so that the alignments would be maintained. IIRC We decided not too when it was realized that we would have to manually adjust every time we ma

[Bug fortran/38249] read(*,*) seems to have broken

2008-11-24 Thread kargl at gcc dot gnu dot org
--- Comment #9 from kargl at gcc dot gnu dot org 2008-11-24 19:52 --- (In reply to comment #8) > I don't mean to be combative, but if EVERYTHING (glibc etc) needs to be build > with -malign-double, not just fortran programs, then IMHO the flag is useless > and should be removed. I've

[Bug fortran/38249] read(*,*) seems to have broken

2008-11-24 Thread ronis at ronispc dot chem dot mcgill dot ca
--- Comment #8 from ronis at ronispc dot chem dot mcgill dot ca 2008-11-24 19:36 --- I don't mean to be combative, but if EVERYTHING (glibc etc) needs to be build with -malign-double, not just fortran programs, then IMHO the flag is useless and should be removed. I've been using this

[Bug fortran/38249] read(*,*) seems to have broken

2008-11-24 Thread pinskia at gcc dot gnu dot org
--- Comment #7 from pinskia at gcc dot gnu dot org 2008-11-24 19:32 --- Not just all your modules but libgfortran also and all of glibc etc. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/38249] read(*,*) seems to have broken

2008-11-24 Thread ronis at ronispc dot chem dot mcgill dot ca
--- Comment #6 from ronis at ronispc dot chem dot mcgill dot ca 2008-11-24 19:29 --- It works without -malign-double, but has worked with it for years. I understand that all modules (even thouse in MY libraries) have to be compiled with the same flags, but nothing seems to imply that t

[Bug fortran/38249] read(*,*) seems to have broken

2008-11-24 Thread kargl at gcc dot gnu dot org
--- Comment #5 from kargl at gcc dot gnu dot org 2008-11-24 19:22 --- (In reply to comment #3) > > Now for the more difficult part. > > I'll attach a tar file containing a sample program and a makefile. It turns > out that the problem isn't with the read at all, rather it arises whe

[Bug fortran/38249] read(*,*) seems to have broken

2008-11-24 Thread ronis at ronispc dot chem dot mcgill dot ca
--- Comment #4 from ronis at ronispc dot chem dot mcgill dot ca 2008-11-24 19:08 --- Created an attachment (id=16764) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16764&action=view) sample source and makefile Running make or make DEBUG=x will generate the program. When you run

[Bug fortran/38249] read(*,*) seems to have broken

2008-11-24 Thread ronis at ronispc dot chem dot mcgill dot ca
--- Comment #3 from ronis at ronispc dot chem dot mcgill dot ca 2008-11-24 19:07 --- OK, here's the information you requested: gfortran -v: Target: i686-pc-linux-gnu Configured with: ../gcc/configure --host=i686-pc-linux-gnu --prefix=/usr --with-gnu-as --enable-shared --with-gnu-ld --

[Bug fortran/38249] read(*,*) seems to have broken

2008-11-24 Thread burnus at gcc dot gnu dot org
--- Comment #2 from burnus at gcc dot gnu dot org 2008-11-24 17:07 --- Regarding : Standard Fortran does not allow tabs, as extension gfortran does. Thus you do not need to change the code (though it does not harm to be standard compliant - that is what the warning tells you). But one ne

[Bug fortran/38249] read(*,*) seems to have broken

2008-11-24 Thread kargl at gcc dot gnu dot org
--- Comment #1 from kargl at gcc dot gnu dot org 2008-11-24 17:00 --- (In reply to comment #0) > I have some legacy code that I just tried compiling with gfortan (on a > i686-linux-slackware-12.1 box). There were a large number of warnings of the > type: > > Warning: Nonconforming tab