public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: pmw@uk.research.att.com (Paul Webster)
To: gcc-help@gcc.gnu.org
Subject: Functions using attribute `noreturn'...
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <200002021707.RAA14128@rocoto> (raw)
Message-ID: <20000401000000.EeDdd0YphI5_osrUx17I9q2IMIkdqR2pgWmaQ0LrLGM@z> (raw)

I'm currently in the process of porting GCC and am trying to optimise my code
for function prologues and epilogues.

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.

Is there any way I can find out whether the current function has been declared
with this attribute? (Similarly, for other attributes, such as interrupt). This
would be in the C support code, not in the machine description (.md) file. Is
there a GCC support routine I can call, or is it more involved?

Thanks in advance for any help.

   Paul


==============================================================================
                          AT&T Laboratories Cambridge
------------------------------------------------------------------------------
    Dr. Paul Webster, 24a Trumpington Street, Cambridge, CB2 1QA, England.
    Tel: +44 (0)1223 343 218                       Fax: +44 (0)1223 313542
==============================================================================

             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 [this message]
2000-02-02 14:23 ` Jeffrey A Law
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=200002021707.RAA14128@rocoto \
    --to=pmw@uk.research.att.com \
    --cc=gcc-help@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).