public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/55022] [4.8 Regression] air.f90 is miscompliled with -m64 -O2 -fgraphite-identity after revision 190619
Date: Mon, 22 Oct 2012 14:25:00 -0000	[thread overview]
Message-ID: <bug-55022-4-fXhKvKKNVI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55022-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-10-22 14:24:51 UTC ---
Created attachment 28507
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28507
compressed archive for the test

The attachment contains the original source air_main.f90 without the
subroutines botwall and topwall which are in the files botwall.f90 and
topwall.f90, and the files datax.inp and datay.inp needed to run the test. It
can be used as

gfc -c -O2 -fgraphite-identity air_main.f90
gfortran -c -O2 -fgraphite-identity botwall.f90 topwall.f90
gfc air_main.o botwall.o topwall.o

With gfc any post r190619 gfortran and gfortran any version pre r188694, this
will give a working executable. If botwall.f90 and/or topwall.f90 is compiled
with a post r190619 gfortran, the executable will give NANs.


  reply	other threads:[~2012-10-22 14:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 13:53 [Bug tree-optimization/55022] New: " dominiq at lps dot ens.fr
2012-10-22 14:25 ` dominiq at lps dot ens.fr [this message]
2012-10-23 13:36 ` [Bug tree-optimization/55022] " dominiq at lps dot ens.fr
2012-11-25 15:52 ` rguenth at gcc dot gnu.org
2013-01-04  3:11 ` pinskia at gcc dot gnu.org
2013-01-04  7:29 ` dominiq at lps dot ens.fr
2013-02-05 15:58 ` aldyh at gcc dot gnu.org
2013-02-05 16:01 ` dominiq at lps dot ens.fr
2013-02-05 16:11 ` grosser at gcc dot gnu.org
2013-02-05 23:52 ` aldyh at gcc dot gnu.org
2013-02-06 18:19 ` aldyh at gcc dot gnu.org
2013-02-06 21:08 ` aldyh at gcc dot gnu.org
2013-02-07 14:58 ` dominiq at lps dot ens.fr
2013-02-07 15:11 ` dominiq at lps dot ens.fr
2013-02-20 13:59 ` rguenth at gcc dot gnu.org
2013-03-22 14:42 ` [Bug tree-optimization/55022] [4.8/4.9 " jakub at gcc dot gnu.org
2013-05-31 10:57 ` jakub at gcc dot gnu.org
2013-10-16  9:48 ` jakub at gcc dot gnu.org
2014-01-17 12:34 ` rguenth at gcc dot gnu.org
2014-04-10 16:01 ` mircea.namolaru at inria dot fr
2014-04-11 11:02 ` rguenth at gcc dot gnu.org
2014-04-11 11:10 ` kargov at gmail dot com
2014-04-11 11:28 ` rguenther at suse dot de
2014-04-11 11:32 ` kargov at gmail dot com
2014-04-11 11:33 ` rguenth at gcc dot gnu.org
2014-04-11 11:43 ` kargov at gmail dot com
2014-04-11 13:03 ` kargov at gmail dot com
2014-04-14  8:11 ` [Bug tree-optimization/55022] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-04-22 13:34 ` [Bug tree-optimization/55022] [4.8 " rguenth at gcc dot gnu.org
2014-04-23  8:58 ` mircea.namolaru at inria dot fr
2014-05-06 12:01 ` rguenth at gcc dot gnu.org
2014-05-06 12:02 ` rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-55022-4-fXhKvKKNVI@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).