public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/29950] Generated code changes after unrelated edits in source.
Date: Sat, 29 Mar 2008 00:57:00 -0000	[thread overview]
Message-ID: <20080329005707.20829.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29950-12956@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from pinskia at gcc dot gnu dot org  2008-03-29 00:57 -------
This is working as designed, the unrelated edits are really related as we base
stuff on the DECL UID which we assign based on the order.

We only promise the same generated code for the same preprocessed source. 
Otherwise you can never do an ordering in a quick way. DECL UID are stable for
rerunning of the compiler so obviously adding a function or two will change the
UID since the functions are decls too.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


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


      parent reply	other threads:[~2008-03-29  0:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 22:56 [Bug rtl-optimization/29950] New: " vda dot linux at googlemail dot com
2006-11-22 22:57 ` [Bug rtl-optimization/29950] " vda dot linux at googlemail dot com
2006-11-22 22:59 ` vda dot linux at googlemail dot com
2006-11-24  2:51 ` pinskia at gcc dot gnu dot org
2007-07-21 23:42 ` vda dot linux at googlemail dot com
2007-08-28 14:49 ` vda dot linux at googlemail dot com
2007-08-31  1:47 ` pinskia at gcc dot gnu dot org
2007-08-31 11:30 ` vda dot linux at googlemail dot com
2008-03-29  0:57 ` pinskia at gcc dot gnu dot org [this message]

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=20080329005707.20829.qmail@sourceware.org \
    --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).