[Bug fortran/38323] gfortran.dg/parameter_array_init_3.f90 -O compilation test ICEs at -m32 and -m64

2008-12-01 Thread jvdelisle at gcc dot gnu dot org
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2008-12-02 03:41 --- I meant elusive in the sense that we have not found the actual cause. We are only seeing a symptom. I have seen a memory leak on x86-64 and segfault on PPC64-linux. That was quite some time ago. --

[Bug fortran/38323] gfortran.dg/parameter_array_init_3.f90 -O compilation test ICEs at -m32 and -m64

2008-11-30 Thread jvdelisle at gcc dot gnu dot org
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2008-12-01 02:11 --- Try this: gdb --args f951 parameter_array_init_3.f90 r bt My experiance with this bug is that it segfaults at a place away from where the actual bug is. This one has been very very elusive. --

[Bug fortran/38323] gfortran.dg/parameter_array_init_3.f90 -O compilation test ICEs at -m32 and -m64

2008-11-30 Thread ebotcazou at gcc dot gnu dot org
--- Comment #4 from ebotcazou at gcc dot gnu dot org 2008-12-01 07:26 --- My experiance with this bug is that it segfaults at a place away from where the actual bug is. This one has been very very elusive. See PR 37469 for a simple method to exhibit the problem. --

[Bug fortran/38323] gfortran.dg/parameter_array_init_3.f90 -O compilation test ICEs at -m32 and -m64

2008-11-29 Thread howarth at nitro dot med dot uc dot edu
--- Comment #1 from howarth at nitro dot med dot uc dot edu 2008-11-30 03:12 --- Since the segfault is in f91, how can I obtain a backtrace for this? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38323

[Bug fortran/38323] gfortran.dg/parameter_array_init_3.f90 -O compilation test ICEs at -m32 and -m64

2008-11-29 Thread kargl at gcc dot gnu dot org
--- Comment #2 from kargl at gcc dot gnu dot org 2008-11-30 03:51 --- *** This bug has been marked as a duplicate of 37469 *** -- kargl at gcc dot gnu dot org changed: What|Removed |Added