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: Fri, 24 Nov 2006 02:51:00 -0000 [thread overview] Message-ID: <20061124025124.14422.qmail@sourceware.org> (raw) In-Reply-To: <bug-29950-12956@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from pinskia at gcc dot gnu dot org 2006-11-24 02:51 ------- Most likely something is being hashed by addresses and then transversing the hashtable or an unstable sort due to using addresses as the last compare. A lot of these issues were fixed in 4.2.0 so this might be fixed already. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29950
next prev parent reply other threads:[~2006-11-24 2:51 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 [this message] 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
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=20061124025124.14422.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: linkBe 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).