From: Segher Boessenkool <segher@kernel.crashing.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] middle-end/81035: Mention that noreturn suppresses tail call optimization
Date: Fri, 21 Sep 2018 18:16:00 -0000 [thread overview]
Message-ID: <20180921181135.GI23155@gate.crashing.org> (raw)
In-Reply-To: <87h8ijktf4.fsf@oldenburg.str.redhat.com>
On Fri, Sep 21, 2018 at 12:59:27PM +0200, Florian Weimer wrote:
> 2018-09-21 Florian Weimer <fweimer@redhat.com>
>
> PR middle-end/81035
> * doc/extend.texi (Common Function Attributes): Mention that
> noreturn suppresses tail call optimization.
> +In order to preserve backtraces, GCC will never turn calls to
> +@code{noreturn} functions into tail calls.
Should we document this? Shouldn't we fix it, instead?
Segher
next prev parent reply other threads:[~2018-09-21 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 11:10 Florian Weimer
2018-09-21 18:16 ` Segher Boessenkool [this message]
2018-09-21 18:29 ` Florian Weimer
2018-09-21 18:36 ` Paul Koning
2018-09-21 18:40 ` Florian Weimer
2018-09-21 22:32 ` Segher Boessenkool
2018-09-21 19:44 ` Jeff Law
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=20180921181135.GI23155@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=fweimer@redhat.com \
--cc=gcc-patches@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).