public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <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: Wed, 06 Feb 2013 18:19:00 -0000 [thread overview]
Message-ID: <bug-55022-4-XDQwhBp73f@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
Aldy Hernandez <aldyh at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #9 from Aldy Hernandez <aldyh at gcc dot gnu.org> 2013-02-06 18:18:54 UTC ---
I'm sorry, but the reporter is going to have to reduce this significantly
before we can debug this. This is a huge mess of spaghetti code with tons of
global and common variables scattered throughout, as well as state being passed
around in files.
Dominique, please reduce this to the smallest amount of reproducible code, so
we can attack this. Avoid reading and writing to files (as I see, these have
only a minimal amount of data anyhow), and global variables if at all possible.
Please only keep the code that is relevant to reproduce the problem.
next prev parent reply other threads:[~2013-02-06 18:19 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 ` [Bug tree-optimization/55022] " dominiq at lps dot ens.fr
2012-10-23 13:36 ` 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 [this message]
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-XDQwhBp73f@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).