[Bug fortran/35873] problem with gfortran -malign-double

2008-04-08 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2008-04-09 00:35 --- If you can separate the I/O functions you need into a separate file and use -malign-double only for those portions that do computations, you can make this work. I can not know from where I sit how important -mali

[Bug fortran/35873] problem with gfortran -malign-double

2008-04-08 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2008-04-08 18:54 --- (In reply to comment #3) > I don't understand how you can call it not a bug when a flag (no matter that > it > changes the ABI) makes valid fortran code not work You have to compile all of libgfortran with -ma

[Bug fortran/35873] problem with gfortran -malign-double

2008-04-08 Thread hjj at ifk dot sdu dot dk
--- Comment #3 from hjj at ifk dot sdu dot dk 2008-04-08 18:50 --- I don't understand how you can call it not a bug when a flag (no matter that it changes the ABI) makes valid fortran code not work It did work under earlier versions of gfotran. -- hjj at ifk dot sdu dot dk chan

[Bug fortran/35873] problem with gfortran -malign-double

2008-04-08 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2008-04-08 16:51 --- This is not a bug, -malign-double changes the ABI. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added --

[Bug fortran/35873] problem with gfortran -malign-double

2008-04-08 Thread hjj at ifk dot sdu dot dk
--- Comment #1 from hjj at ifk dot sdu dot dk 2008-04-08 16:47 --- (In reply to comment #0) > --> gfortran -malign-double test.f; a.out # ERROR: Segmentation violation > --> gfortran test.f; a.out # OK Fix of typo (gcc instead of gfortran) -- http://gcc.gnu.org/bugzilla/show_bug.cg