public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56294] BOOT_CFLAGS='-O2 -g -fno-ipa-sra' leads to bootstrap comparison failure
Date: Sat, 23 Feb 2013 11:37:00 -0000	[thread overview]
Message-ID: <bug-56294-4-Q9X7s1Ving@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56294-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #9 from Martin Jambor <jamborm at gcc dot gnu.org> 2013-02-23 11:37:24 UTC ---
Created attachment 29528
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29528
A simpler patch to fix issue in comment 7

The patch from comment #8 had problems of its own, mainly it does not
take care of the elaborate fancy names that create_access_replacement
creates for the user-created aggregates.

I think that the "SR" names that it leaves in the artificial aggregate
replacements do not have a high enough value to justify another
parameter of get_access_replacement and storing or late-creating fancy
names and so on, so if we do not want to create replacements upfront,
I'd actually prefer this much simpler patch.

However, if we go down this route of creating replacements lazily,
that will mean that replacement declarations may be created in
different order in -g and -g0 runs (exactly in the cases when patch
from comment #8 had to upgrade a debug-only replacement to a real
one), which, if I understand it well, may lead to different ordering
of decl UIDs which in turn may eventually lead to further code
generation differences...


  parent reply	other threads:[~2013-02-23 11:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 10:46 [Bug tree-optimization/56294] New: " jamborm at gcc dot gnu.org
2013-02-12 10:46 ` [Bug tree-optimization/56294] " jamborm at gcc dot gnu.org
2013-02-12 12:28 ` rguenth at gcc dot gnu.org
2013-02-12 18:18 ` jamborm at gcc dot gnu.org
2013-02-12 19:44 ` jamborm at gcc dot gnu.org
2013-02-13 10:56 ` jamborm at gcc dot gnu.org
2013-02-15 16:01 ` jamborm at gcc dot gnu.org
2013-02-18 12:15 ` jakub at gcc dot gnu.org
2013-02-19 14:49 ` jamborm at gcc dot gnu.org
2013-02-23 11:37 ` jamborm at gcc dot gnu.org [this message]
2013-02-23 11:51 ` jamborm at gcc dot gnu.org
2013-02-27 16:11 ` jamborm at gcc dot gnu.org
2013-02-28 12:44 ` jamborm at gcc dot gnu.org
2013-03-01 10:28 ` rguenth at gcc dot gnu.org
2013-03-01 10:32 ` jakub at gcc dot gnu.org
2013-03-04 17:17 ` jamborm at gcc dot gnu.org
2013-03-05 10:03 ` rguenth at gcc dot gnu.org
2013-03-05 12:57 ` rguenth at gcc dot gnu.org
2013-03-05 16:49 ` jamborm at gcc dot gnu.org
2013-03-06  9:45 ` rguenth at gcc dot gnu.org
2013-03-06 11:24 ` rguenth at gcc dot gnu.org
2013-03-06 11:25 ` rguenth at gcc dot gnu.org
2013-03-12  9:09 ` jamborm 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-56294-4-Q9X7s1Ving@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).