public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zadeck at naturalbridge dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/37808] [4.4 Regression]: Revision 141067 breaks Linux/x86 Date: Sun, 12 Oct 2008 21:20:00 -0000 [thread overview] Message-ID: <20081012211914.23365.qmail@sourceware.org> (raw) In-Reply-To: <bug-37808-682@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from zadeck at naturalbridge dot com 2008-10-12 21:19 ------- Subject: Re: [4.4 Regression]: Revision 141067 breaks Linux/x86 Richard Guenther wrote: > On Sun, Oct 12, 2008 at 11:12 PM, Kenneth Zadeck > <zadeck@naturalbridge.com> wrote: > >> andreast at gcc dot gnu dot org wrote: >> >>> ------- Comment #7 from andreast at gcc dot gnu dot org 2008-10-12 20:31 ------- >>> I see a failure on sparc-solaris8/10 too. Configury of stage2 fails. >>> Applying the mentioned patch cures compilation. >>> My sparc config is with multilib. 32-bit/64-bit. >>> >>> >>> >>> >> The problem is that the bb is no longer kept in the df-ref, and is >> instead extracted from the insn. >> This particular problem was caused by insns being deleted in a pass that >> defers rescanning but that also changes register numbers. The fix >> checks to make sure the insn is still in a basic block before trying to >> mark the block as being dirty. >> > > Ok. I think it's odd that we keep refs to deleted insns - but that's probably > because of the deferred re-scan, right? > > Thanks, > Richard. > yes, this only is because of the deferred rescan. committed as revision 14178. kenny > >> 2008-10-12 Kenneth Zadeck <zadeck@naturalbridge.com> >> >> PR middle-end/37808 >> * df-scan.c (df_ref_change_reg_with_loc_1): Added test to make >> sure that ref has valid bb. >> >> Tested by me on both x86-32 and x86-64. Also tested by andreast on >> spark-solaris and by keating. >> >> OK to commit? >> >> kenny >> >> -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37808
next prev parent reply other threads:[~2008-10-12 21:20 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-12 2:02 [Bug bootstrap/37808] New: " hjl dot tools at gmail dot com 2008-10-12 2:03 ` [Bug bootstrap/37808] " hjl dot tools at gmail dot com 2008-10-12 2:21 ` [Bug target/37808] " pinskia at gcc dot gnu dot org 2008-10-12 4:57 ` zadeck at naturalbridge dot com 2008-10-12 16:58 ` gcc-bugzilla at daryl dot haresign dot com 2008-10-12 17:52 ` dominiq at lps dot ens dot fr 2008-10-12 19:45 ` geoffk at gcc dot gnu dot org 2008-10-12 20:32 ` andreast at gcc dot gnu dot org 2008-10-12 21:14 ` zadeck at naturalbridge dot com 2008-10-12 21:18 ` richard dot guenther at gmail dot com 2008-10-12 21:19 ` zadeck at gcc dot gnu dot org 2008-10-12 21:20 ` zadeck at naturalbridge dot com [this message] 2008-10-12 21:23 ` zadeck at naturalbridge dot com
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=20081012211914.23365.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).