From: Florian Weimer <fweimer@redhat.com>
To: Tadeus Prastowo via Libc-help <libc-help@sourceware.org>
Subject: Re: raise() marked __leaf__ is not C-compliant?
Date: Wed, 28 Oct 2020 09:21:45 +0100 [thread overview]
Message-ID: <87v9eu3gme.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CAA1YtmtVEcvOOyo+crpNg=p382hyQv47=K3sv1oPgk-AKnN=QA@mail.gmail.com> (Tadeus Prastowo via Libc-help's message of "Tue, 27 Oct 2020 17:57:47 +0100")
* Tadeus Prastowo via Libc-help:
> With glibc-2.30 raise() being marked __leaf__, the attached C program
> has an undefined behavior because it terminates when compiled with GCC
> using either -O0 or -Os but enters an infinite loop when using -O2.
Yes, I think the leaf attribute is incorrect for raise and similar
functions. throw()/noexcept is questionable as well because the GNU
implementation supports throwing from a synchronous signal handler, as
an extension.
I can't find a Bugzilla bug for this right now, but I think we discussed
it before.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-10-28 8:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 16:57 Tadeus Prastowo
2020-10-27 18:50 ` Adhemerval Zanella
2020-10-28 5:47 ` Tadeus Prastowo
2020-10-28 6:13 ` Tadeus Prastowo
2020-10-28 7:33 ` Tadeus Prastowo
2020-10-28 11:53 ` Adhemerval Zanella
2020-10-28 13:19 ` Tadeus Prastowo
2020-10-28 17:34 ` Adhemerval Zanella
2020-10-28 19:23 ` Tadeus Prastowo
2020-10-28 20:17 ` Adhemerval Zanella
2020-10-29 7:50 ` Tadeus Prastowo
2020-10-28 8:21 ` Florian Weimer [this message]
2020-10-28 12:58 ` Tadeus Prastowo
2020-10-28 17:16 ` Tadeus Prastowo
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=87v9eu3gme.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-help@sourceware.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).