[Bug fortran/32393] gfortran - incorrect run time results

["pinskia at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #28 from pinskia at gmail dot com  2007-06-24 11:12 -------
Subject: Re:  gfortran - incorrect run time results

On 24 Jun 2007 10:51:42 -0000, dominiq at lps dot ens dot fr
<gcc-bugzilla@gcc.gnu.org> wrote:
>
> (1)  when compiled with 4.1, g95 gives ICE on derived type I/O when compiled
> with -O (at least on Mac OSX 10.3.9):

>
> [karma] bug/ice_g95_4.1% g95 -O type_1_red.f90
> type_1_red.f90:3: internal compiler error: Bus error
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://www.g95.org or mail andyv@firstinter.net for instructions.

So what is the backtrace inside the middle-end?  If possible (and
knowing) give the output of the tree dumps (-fdump-tree-all).  If Andy
is blaming us, he might as well report real bugs instead of just
saying it is our bug.  I would say if Andy does not want even to
report any bugs about the middle-end going wrong (or right, see
below), I would strongly recommend you stay away from g95.

> (2) I have an infinite loop with the following code and -O3:
>
> ! { dg-do run }
> ! Program to check corner cases for DO statements.

Try with -fwarpv, I bet this is really a bug in g95's IR.  Can you
provide me (us) with the tree dumps?

> A long time ago, I have reported the problem to Andy who is blaming the gcc
> middle-end, so if someone working in this area have an idea ...!

Some cases are our fault, others are g95's fault and Andy might not
want to say it is his fault if the middle-end optimizes away stuff
based on undefined code (which I bet is happening in the last case).

Thanks,
Andrew Pinski


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32393