public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49519] [4.7 Regression] Revision 175272 miscompiled 447.dealII in SPEC CPU 2006
Date: Wed, 06 Jul 2011 11:54:00 -0000 [thread overview]
Message-ID: <bug-49519-4-64Hq8IzHoA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49519-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49519
--- Comment #21 from rguenther at suse dot de <rguenther at suse dot de> 2011-07-06 11:53:56 UTC ---
On Wed, 6 Jul 2011, kirill.yukhin at intel dot com wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49519
>
> --- Comment #19 from Yukhin Kirill <kirill.yukhin at intel dot com> 2011-07-06 11:49:34 UTC ---
> Created attachment 24701
> --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24701
> Patch to make tailcall check more conservative
>
> Attached patch adds another check for clobbered stack area.
> If address comes from a register - we have no idea about destination address.
> That means we must act in conservative way - address possibly overlaps with
> stack area of interest.
That looks reasonable. Can you bootstrap & test this fix and post it to
gcc-patches?
next prev parent reply other threads:[~2011-07-06 11:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 0:40 [Bug c++/49519] New: " hjl.tools at gmail dot com
2011-06-24 4:41 ` [Bug c++/49519] " hjl.tools at gmail dot com
2011-06-24 8:50 ` rguenth at gcc dot gnu.org
2011-06-24 16:37 ` hjl.tools at gmail dot com
2011-06-25 3:10 ` jason at gcc dot gnu.org
2011-06-29 5:06 ` kirill.yukhin at intel dot com
2011-06-29 12:25 ` kirill.yukhin at intel dot com
2011-06-30 15:12 ` kirill.yukhin at intel dot com
2011-06-30 15:23 ` kirill.yukhin at intel dot com
2011-06-30 15:27 ` kirill.yukhin at intel dot com
2011-06-30 15:37 ` kirill.yukhin at intel dot com
2011-07-05 14:47 ` jason at gcc dot gnu.org
2011-07-05 18:10 ` jason at gcc dot gnu.org
2011-07-06 8:40 ` rguenth at gcc dot gnu.org
2011-07-06 8:48 ` kirill.yukhin at intel dot com
2011-07-06 10:26 ` kirill.yukhin at intel dot com
2011-07-06 10:30 ` [Bug middle-end/49519] " rguenth at gcc dot gnu.org
2011-07-06 10:36 ` kirill.yukhin at intel dot com
2011-07-06 10:39 ` rguenth at gcc dot gnu.org
2011-07-06 10:50 ` rguenth at gcc dot gnu.org
2011-07-06 11:51 ` kirill.yukhin at intel dot com
2011-07-06 11:51 ` kirill.yukhin at intel dot com
2011-07-06 11:54 ` rguenther at suse dot de [this message]
2011-07-06 11:59 ` kirill.yukhin at intel dot com
2011-07-06 19:39 ` hjl.tools at gmail dot com
2011-07-08 13:12 ` hjl at gcc dot gnu.org
2011-07-08 23:39 ` janis at gcc dot gnu.org
2011-07-11 11:55 ` rguenth at gcc dot gnu.org
2011-07-12 4:38 ` ian at airs dot com
2011-07-12 4:56 ` ian at airs dot com
2011-07-12 8:37 ` rguenther at suse dot de
2011-07-12 8:43 ` ebotcazou at gcc dot gnu.org
2011-07-12 15:07 ` janis at gcc dot gnu.org
2011-08-15 14:27 ` hjl.tools at gmail dot com
2011-11-19 11:47 ` amylaar 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-49519-4-64Hq8IzHoA@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).