public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eggert at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/48968] incorrect warning about longjmp/vfork clobbering a local (-W -O2, x86-64)
Date: Fri, 01 Jun 2012 20:42:00 -0000 [thread overview]
Message-ID: <bug-48968-4-1TZLYzOvi5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48968-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48968
eggert at gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|4.6.0 |4.7.0
--- Comment #6 from eggert at gnu dot org 2012-06-01 20:42:42 UTC ---
I just now ran into the bug again when compiling a new Emacs version and so am
following up.
The function read_char_minibuf_menu_prompt does not call setjmp. Apparently
GCC is inlining the function into some other place and then complaining that
the result is unsafe, but this sort of inlining would be incorrect if it
actually made the code unsafe, so the diagnostic is either incorrect, or (if
correct) indicates the possibility that the wrong code has been generated. I
have verified that the problem is still there with GCC 4.7.0 and so I'll try to
change the version number in this bug report.
next prev parent reply other threads:[~2012-06-01 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 20:04 [Bug c/48968] New: " eggert at gnu dot org
2011-05-11 20:00 ` [Bug c/48968] " eggert at gnu dot org
2011-05-12 11:07 ` rguenth at gcc dot gnu.org
2011-05-12 13:54 ` schwab@linux-m68k.org
2011-05-12 19:11 ` jakub at gcc dot gnu.org
2011-05-12 20:22 ` eggert at gnu dot org
2012-06-01 20:42 ` eggert at gnu dot org [this message]
2012-06-01 21:19 ` eggert at gnu dot org
2014-01-19 18:01 ` mpolacek at gcc dot gnu.org
2014-01-19 18:34 ` eggert at gnu dot org
2014-01-19 20:31 ` mpolacek 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-48968-4-1TZLYzOvi5@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).