public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/59039] Undocumented __builtin_longjmp/__builtin_setjmp
Date: Fri, 08 Nov 2013 10:21:00 -0000 [thread overview]
Message-ID: <bug-59039-4-F6hERv1Frr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59039-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59039
--- Comment #17 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Richard Biener from comment #16)
> > I couldn't find anything in GCC manual.
>
> See tm.texi / md.texi.
This is the only thing I found:
-- Macro: DONT_USE_BUILTIN_SETJMP
Define this macro to 1 if the 'setjmp'/'longjmp'-based scheme
should use the 'setjmp'/'longjmp' functions from the C library
instead of the '__builtin_setjmp'/'__builtin_longjmp' machinery.
It doesn't say they can't be used in the same
function, the size of the jump buffer, nor what
each field in the jump buffer is used for.
next prev parent reply other threads:[~2013-11-08 10:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 12:51 [Bug other/59039] New: " hjl.tools at gmail dot com
2013-11-07 14:49 ` [Bug other/59039] " rguenth at gcc dot gnu.org
2013-11-07 14:52 ` rguenth at gcc dot gnu.org
2013-11-07 14:53 ` hjl.tools at gmail dot com
2013-11-07 14:59 ` [Bug c/59039] " rguenth at gcc dot gnu.org
2013-11-07 15:02 ` rguenth at gcc dot gnu.org
2013-11-07 15:03 ` hjl.tools at gmail dot com
2013-11-07 15:16 ` ebotcazou at gcc dot gnu.org
2013-11-07 15:32 ` hjl.tools at gmail dot com
2013-11-07 15:49 ` ebotcazou at gcc dot gnu.org
2013-11-07 16:27 ` hjl.tools at gmail dot com
2013-11-07 17:18 ` ebotcazou at gcc dot gnu.org
2013-11-07 22:54 ` ebotcazou at gcc dot gnu.org
2013-11-07 22:56 ` hjl.tools at gmail dot com
2013-11-08 8:47 ` rguenth at gcc dot gnu.org
2013-11-08 10:21 ` hjl.tools at gmail dot com [this message]
2013-11-08 10:53 ` ebotcazou at gcc dot gnu.org
2013-11-08 16:52 ` hjl.tools at gmail dot com
2013-11-08 19:15 ` schwab@linux-m68k.org
2013-11-08 19:52 ` bviyer at gcc dot gnu.org
2013-11-08 21:05 ` hjl.tools at gmail dot com
2013-11-09 12:33 ` ebotcazou at gcc dot gnu.org
2014-01-06 17:40 ` rth at gcc dot gnu.org
2014-01-07 9:09 ` ebotcazou 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-59039-4-F6hERv1Frr@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).