public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/43013] [4.5 Regression] "warning: 'saved_stack.1' is used uninitialized in this function" with -fstack-check
Date: Thu, 11 Feb 2010 18:28:00 -0000 [thread overview]
Message-ID: <20100211182808.26813.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43013-14164@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from pinskia at gcc dot gnu dot org 2010-02-11 18:28 -------
Note this works correctly on targets that define STACK_CHECK_BUILTIN to be 1.
This includes the spu target. The main reason is that the code goes through a
different path.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
GCC target triplet| |i?86-*-* x86_64-*-*
| |powerpc*-*-*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43013
next prev parent reply other threads:[~2010-02-11 18:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 22:17 [Bug tree-optimization/43013] New: "warning: 'saved_stack.1' is used uninitialized in this function" with -fstack-protector zsojka at seznam dot cz
2010-02-09 22:21 ` [Bug tree-optimization/43013] " zsojka at seznam dot cz
2010-02-09 23:33 ` [Bug tree-optimization/43013] [4.5 Regression] "warning: 'saved_stack.1' is used uninitialized in this function" with -fstack-check pinskia at gcc dot gnu dot org
2010-02-10 9:11 ` [Bug middle-end/43013] [4.4/4.5 " jakub at gcc dot gnu dot org
2010-02-11 12:23 ` [Bug middle-end/43013] [4.5 " ebotcazou at gcc dot gnu dot org
2010-02-11 16:55 ` rguenth at gcc dot gnu dot org
2010-02-11 18:28 ` pinskia at gcc dot gnu dot org [this message]
2010-02-11 18:55 ` ebotcazou at gcc dot gnu dot org
2010-04-30 9:25 ` [Bug middle-end/43013] [4.5/4.6 " jakub at gcc dot gnu dot org
[not found] <bug-43013-4@http.gcc.gnu.org/bugzilla/>
2012-05-26 14:24 ` [Bug middle-end/43013] [4.5 regression] " ebotcazou at gcc dot gnu.org
2012-07-02 10:47 ` 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=20100211182808.26813.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).