public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou 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 12:23:00 -0000 [thread overview] Message-ID: <20100211122330.15045.qmail@sourceware.org> (raw) In-Reply-To: <bug-43013-14164@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from ebotcazou at gcc dot gnu dot org 2010-02-11 12:23 ------- I'll write a book about -fstack-check someday... -fstack-check was severely broken during the GCC3 -> GCC4 transition and, despite years of patches posting and pinging, only GCC 4.5 has the beginning of a working implementation, so anything between 4.0 and 4.4 must be forgotten since totally broken. And, again despite posted patches, the 4.5 implementation only restores the old implementation available in the 3.x series, which doesn't work for this case: eric@atlantis:~/build/gcc/native32> ~/install/gcc-3_4-branch/bin/gcc -v Reading specs from /home/eric/install/gcc-3_4-branch/lib/gcc/x86_64-suse-linux/3.4.6/specs Configured with: /home/eric/svn/gcc-3_4-branch/configure x86_64-suse-linux --prefix=/home/eric/install/gcc-3_4-branch --enable-languages=c,c++,objc,f77,java,ada --enable-__cxa_atexit Thread model: posix gcc version 3.4.6 eric@atlantis:~/build/gcc/native32> ~/install/gcc-3_4-branch/bin/gcc -m32 -S pr43013.c eric@atlantis:~/build/gcc/native32> ~/install/gcc-3_4-branch/bin/gcc -m32 -S pr43013.c -fstack-check pr43013.c: In function `foo': pr43013.c:6: error: label 'lab' used before containing binding contour Granted, we now generate wrong code instead of erroring out, but it's again a fallout of the GCC3 -> GCC4 breakage, not of my patches. This will be fixed once the improved implementation is merged. ETA is 4.6, for x86/x86-64 at least. -- ebotcazou at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[4.4/4.5 Regression] |[4.5 Regression] "warning: |"warning: 'saved_stack.1' is|'saved_stack.1' is used |used uninitialized in this |uninitialized in this |function" with -fstack-check|function" with -fstack-check http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43013
next prev parent reply other threads:[~2010-02-11 12:23 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 ` ebotcazou at gcc dot gnu dot org [this message] 2010-02-11 16:55 ` [Bug middle-end/43013] [4.5 " rguenth at gcc dot gnu dot org 2010-02-11 18:28 ` pinskia at gcc dot gnu dot org 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=20100211122330.15045.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).