public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/42509] [4.5 Regression] bootstrap failure in stage3 (integer overflow in preprocessor expression) Date: Fri, 02 Apr 2010 12:33:00 -0000 [thread overview] Message-ID: <20100402123334.26889.qmail@sourceware.org> (raw) In-Reply-To: <bug-42509-11764@http.gcc.gnu.org/bugzilla/> ------- Comment #22 from rguenth at gcc dot gnu dot org 2010-04-02 12:33 ------- Or a combination of both. In particular the code doesn't account for the negative offsets we offset the spill-slot decl with when trying to handle a NULL MEM_OFFSET conservatively. I wonder what sizex / sizey is for the spill-slot-decl, or rather what mode or size it has ... Least pessimizing patch follows, it looks like nobody else would disambiguate spill slots otherwise (apart from the tree oracle calls). Index: gcc/alias.c =================================================================== --- gcc/alias.c (revision 157942) +++ gcc/alias.c (working copy) @@ -2147,6 +2147,13 @@ nonoverlapping_memrefs_p (const_rtx x, c if (exprx == 0 || expry == 0) return 0; + /* For spill-slot accesses make sure we have valid offsets. */ + if ((exprx == get_spill_slot_decl (false) + && ! MEM_OFFSET (x)) + || (expry == get_spill_slot_decl (false) + && ! MEM_OFFSET (y))) + return 0; + /* If both are field references, we may be able to determine something. */ if (TREE_CODE (exprx) == COMPONENT_REF && TREE_CODE (expry) == COMPONENT_REF -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42509
next prev parent reply other threads:[~2010-04-02 12:33 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-26 12:03 [Bug target/42509] New: " doko at ubuntu dot com 2009-12-29 10:09 ` [Bug target/42509] " ramana at gcc dot gnu dot org 2009-12-30 23:55 ` ramana at gcc dot gnu dot org 2009-12-31 15:21 ` [Bug target/42509] [4.5 Regression] " rguenth at gcc dot gnu dot org 2010-01-06 12:26 ` ramana at gcc dot gnu dot org 2010-01-07 13:53 ` debian-gcc at lists dot debian dot org 2010-03-15 13:23 ` rguenth at gcc dot gnu dot org 2010-03-15 17:36 ` laurent at guerby dot net 2010-03-16 8:57 ` ramana at gcc dot gnu dot org 2010-03-16 13:56 ` rguenth at gcc dot gnu dot org 2010-04-01 15:03 ` rearnsha at gcc dot gnu dot org 2010-04-01 15:11 ` rearnsha at gcc dot gnu dot org 2010-04-01 15:32 ` rearnsha at gcc dot gnu dot org 2010-04-01 15:55 ` ramana at gcc dot gnu dot org 2010-04-01 17:11 ` ramana at gcc dot gnu dot org 2010-04-01 19:31 ` rearnsha at gcc dot gnu dot org 2010-04-01 22:04 ` rearnsha at gcc dot gnu dot org 2010-04-01 22:44 ` rearnsha at gcc dot gnu dot org 2010-04-01 23:34 ` [Bug middle-end/42509] " rearnsha at gcc dot gnu dot org 2010-04-02 0:02 ` ramana at gcc dot gnu dot org 2010-04-02 8:08 ` ramana at gcc dot gnu dot org 2010-04-02 12:09 ` rguenth at gcc dot gnu dot org 2010-04-02 12:15 ` rguenth at gcc dot gnu dot org 2010-04-02 12:33 ` rguenth at gcc dot gnu dot org [this message] 2010-04-02 13:54 ` rguenth at gcc dot gnu dot org 2010-04-02 15:20 ` rguenth at gcc dot gnu dot org 2010-04-02 16:15 ` rguenth at gcc dot gnu dot org 2010-04-03 17:15 ` rguenth at gcc dot gnu dot org 2010-04-03 17:15 ` rguenth at gcc dot gnu dot org 2010-04-12 19:56 ` [Bug middle-end/42509] [4.4 " steven at gcc dot gnu dot org 2010-04-12 19:58 ` [Bug middle-end/42509] [4.4 Regression] nonoverlapping_memrefs_p misinterprets NULL MEM_OFFSET as const0_rtx steven at gcc dot gnu dot org 2010-04-30 8:58 ` jakub at gcc dot gnu dot org 2010-07-28 18:00 ` uweigand at gcc dot gnu dot org 2010-07-28 18:01 ` uweigand 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=20100402123334.26889.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).