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 tree-optimization/43220] [4.3/4.4 Regression] Paritially optimized __builtin_save_stack/__builtin_restore_stack causes segmentation fault
Date: Mon, 01 Mar 2010 16:57:00 -0000 [thread overview]
Message-ID: <20100301165723.15277.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43220-15361@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from rguenth at gcc dot gnu dot org 2010-03-01 16:57 -------
Subject: Bug 43220
Author: rguenth
Date: Mon Mar 1 16:57:02 2010
New Revision: 157149
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=157149
Log:
2010-03-01 Richard Guenther <rguenther@suse.de>
PR tree-optimization/43220
* tree-ssa-ccp.c (optimize_stack_restore): Do not optimize
BUILT_IN_STACK_{SAVE,RESTORE} around alloca.
* gcc.c-torture/execute/pr43220.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.c-torture/execute/pr43220.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-ccp.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43220
next prev parent reply other threads:[~2010-03-01 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 14:07 [Bug tree-optimization/43220] New: " bmei at broadcom dot com
2010-03-01 15:00 ` [Bug tree-optimization/43220] [4.3/4.4/4.5 Regression] " rguenth at gcc dot gnu dot org
2010-03-01 15:16 ` rguenth at gcc dot gnu dot org
2010-03-01 16:57 ` rguenth at gcc dot gnu dot org [this message]
2010-03-01 16:57 ` [Bug tree-optimization/43220] [4.3/4.4 " rguenth at gcc dot gnu dot org
2010-03-02 7:44 ` jakub at gcc dot gnu dot org
2010-03-02 7:47 ` [Bug tree-optimization/43220] [4.3 " jakub at gcc dot gnu dot org
2010-04-20 14:25 ` rguenth at gcc dot gnu dot org
2010-04-20 14:25 ` rguenth 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=20100301165723.15277.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: 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).