public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: Ilyes Gouta <ilyes.gouta@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: __declspec(naked) and function body size
Date: Sat, 08 Dec 2007 19:46:00 -0000	[thread overview]
Message-ID: <475AF47C.F78F600@dessent.net> (raw)
In-Reply-To: <475AB169.1000905@gmail.com>

Ilyes Gouta wrote:

> Is it possible using GCC? If yes, could you please tell me how?

There is __attribute__((naked)) but it's not supported for x86.  I think
the feeling is that gcc should be able to detect when a prologue is not
necessary on its own and just not emit it, and that forcably disabling
the prologue just results in horribly broken code if the function
happens to require a spill.  See also
<http://gcc.gnu.org/ml/gcc/2004-02/threads.html#00939>.

Brian

  reply	other threads:[~2007-12-08 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08 15:01 Ilyes Gouta
2007-12-08 19:46 ` Brian Dessent [this message]
2007-12-08 21:58   ` Ilyes Gouta
2007-12-08 23:26     ` Brian Dessent
2007-12-09  6:51       ` Ilyes Gouta

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=475AF47C.F78F600@dessent.net \
    --to=brian@dessent.net \
    --cc=gcc-help@gcc.gnu.org \
    --cc=ilyes.gouta@gmail.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).