public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/48702] [4.6/4.7 Regression] optimization regression with gcc-4.6 on x86_64-unknown-linux-gnu
Date: Thu, 26 May 2011 13:03:00 -0000 [thread overview]
Message-ID: <bug-48702-4-HMaQPK4NwH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48702-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48702
--- Comment #27 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-05-26 13:01:50 UTC ---
Author: rguenth
Date: Thu May 26 13:01:48 2011
New Revision: 174282
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=174282
Log:
2011-05-26 Richard Guenther <rguenther@suse.de>
PR tree-optimization/48702
* tree-ssa-address.c (create_mem_ref_raw): Create MEM_REFs
only when we know the base address is within bounds.
* tree-ssa-alias.c (indirect_ref_may_alias_decl_p): Do not
assume the base address of TARGET_MEM_REFs is in bounds.
* gcc.dg/torture/pr48702.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/torture/pr48702.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-address.c
trunk/gcc/tree-ssa-alias.c
next prev parent reply other threads:[~2011-05-26 13:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 14:12 [Bug rtl-optimization/48702] New: " mariah.lenox at gmail dot com
2011-04-20 14:29 ` [Bug rtl-optimization/48702] " rguenth at gcc dot gnu.org
2011-04-20 14:32 ` [Bug rtl-optimization/48702] [4.6 Regression] " rguenth at gcc dot gnu.org
2011-04-20 14:39 ` rguenth at gcc dot gnu.org
2011-04-20 15:08 ` [Bug rtl-optimization/48702] [4.6/4.7 " rguenth at gcc dot gnu.org
2011-04-21 10:48 ` rguenth at gcc dot gnu.org
2011-04-21 11:06 ` [Bug tree-optimization/48702] " rguenth at gcc dot gnu.org
2011-04-21 11:50 ` rakdver at gcc dot gnu.org
2011-04-21 12:32 ` rguenth at gcc dot gnu.org
2011-04-21 12:39 ` rguenth at gcc dot gnu.org
2011-04-21 12:58 ` rakdver at kam dot mff.cuni.cz
2011-04-21 13:06 ` rguenther at suse dot de
2011-04-21 13:35 ` rakdver at kam dot mff.cuni.cz
2011-04-21 16:22 ` xinliangli at gmail dot com
2011-05-12 12:10 ` rguenth at gcc dot gnu.org
2011-05-17 17:40 ` xinliangli at gmail dot com
2011-05-17 19:42 ` rakdver at kam dot mff.cuni.cz
2011-05-17 20:43 ` xinliangli at gmail dot com
2011-05-17 20:53 ` rakdver at kam dot mff.cuni.cz
2011-05-17 21:29 ` xinliangli at gmail dot com
2011-05-18 9:18 ` rguenther at suse dot de
2011-05-18 16:17 ` xinliangli at gmail dot com
2011-05-19 5:30 ` xinliangli at gmail dot com
2011-05-25 11:03 ` rguenth at gcc dot gnu.org
2011-05-25 11:06 ` rguenth at gcc dot gnu.org
2011-05-25 14:00 ` rguenth at gcc dot gnu.org
2011-05-26 10:05 ` rguenth at gcc dot gnu.org
2011-05-26 11:14 ` rguenth at gcc dot gnu.org
2011-05-26 13:03 ` rguenth at gcc dot gnu.org [this message]
2011-05-26 13:23 ` [Bug tree-optimization/48702] [4.6 " rguenth at gcc dot gnu.org
2011-06-06 10:14 ` rguenth at gcc dot gnu.org
2011-06-06 10:20 ` rguenth 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-48702-4-HMaQPK4NwH@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).