This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: ../../../gcc/f/target.c:217: failed assertion `alignment > 0'



  In message <199903011838.NAA24225@hiauly1.hia.nrc.ca>you write:
  > The current CVS source fails many g77 tests in the testsuite under hpux9.01
  > because of the following error:
  > 
  > spawn /xxx/gnu/egcs-2.93.10/objdir/gcc/g77 -B/xxx/gnu/egcs-2.93.10/objdir/gcc/ /
  > xxx/gnu/egcs-2.93.10/gcc/testsuite/g77.f-torture/compile/980310-2.f -w -O0 -L/xx
  > x/gnu/egcs-2.93.10/objdir/hppa1.1-hp-hpux9.01/libf2c -c -o /xxx/gnu/egcs-2.93.10
  > /objdir/gcc/testsuite/980310-2.o ^M
  > ../../../gcc/f/target.c:217: failed assertion `alignment > 0'^M
  > g77: Internal compiler error: program f771 got fatal signal 6^M
  > compiler exited with status 1
  > output is:
  > ../../../gcc/f/target.c:217: failed assertion `alignment > 0'^M
  > g77: Internal compiler error: program f771 got fatal signal 6^M
Yup.  GCC is mis-compiling a routine in the fortran front-end.

The same bug is also causing the 930603-1.c execution failures on the x86.

This was a bug brought over in the last gcc2 merge (gcc2-980929).  Ironically
this bug was fixed in the gcc2 sources on 980930.

Anyway, I've brought over the fix from the gcc2 tree.  This problem should be
fixed.

jeff


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]