From: Richard Henderson <rth@redhat.com>
To: mstr@nemesishook.cjb.net
Cc: gcc@gcc.gnu.org
Subject: Re: REQ: naked attribute on x86
Date: Tue, 28 Jan 2003 10:01:00 -0000 [thread overview]
Message-ID: <20030128062620.GA19109@redhat.com> (raw)
In-Reply-To: <200301261926.h0QJQiG47589@mail.cjb.net>
On Sun, Jan 26, 2003 at 12:26:44PM -0700, mstr@nemesishook.cjb.net wrote:
> Hi, I guess that this must have been asked for at some point,
> but please make __attribute__((naked)) work on x86 target. Yes,
> it's probably not very portable, but those who use it, should
> know what they are doing anyway.
I will not. I think this is the worst possible extension.
I know it exists for some gcc ports, but even there I think
it is a mistake.
You *cannot* write correct code to go with __attribute__((naked)).
If you're trying to use it, and only put one __asm__ in the
function, yes that will work, but why didn't you just define
the *entire* function in assembly?
r~
prev parent reply other threads:[~2003-01-28 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-26 22:00 mstr
2003-01-28 10:01 ` Richard Henderson [this message]
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=20030128062620.GA19109@redhat.com \
--to=rth@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mstr@nemesishook.cjb.net \
/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).