From: Jeffrey A Law <law@cygnus.com>
To: pmw@uk.research.att.com (Paul Webster)
Cc: gcc-help@gcc.gnu.org
Subject: Re: Functions using attribute `noreturn'...
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <3261.949529923@upchuck> (raw)
Message-ID: <20000401000000.eNvB_ae5hFm89v6q3zQnWyoigwUjcAVogInF0a4Kc2Y@z> (raw)
In-Reply-To: <200002021707.RAA14128@rocoto>
In message < 200002021707.RAA14128@rocoto >you write:
> To minimise the amount of code output, I would like to check to see if the
> current function is declared with the __noreturn__ attribute. If it is,
> then I don't need to do output any of the function return code or
> save/restore any registers that otherwise would be.
This will happen automatically if you are using RTL prologues and epilogues.
The code which emits the epilogue will notice that the exit block has no
true predecessors and thus the epilogue code is unnecessary and never added
to the insn stream.
jeff
next prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-02 9:08 Paul Webster
2000-02-02 14:23 ` Jeffrey A Law [this message]
2000-04-01 0:00 ` Jeffrey A Law
2000-04-01 0:00 ` Paul Webster
2000-02-02 11:56 Ralf Guetlein
2000-04-01 0:00 ` Ralf Guetlein
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=3261.949529923@upchuck \
--to=law@cygnus.com \
--cc=gcc-help@gcc.gnu.org \
--cc=pmw@uk.research.att.com \
/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).