* REQ: naked attribute on x86
@ 2003-01-26 22:00 mstr
2003-01-28 10:01 ` Richard Henderson
0 siblings, 1 reply; 2+ messages in thread
From: mstr @ 2003-01-26 22:00 UTC (permalink / raw)
To: gcc
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: REQ: naked attribute on x86
2003-01-26 22:00 REQ: naked attribute on x86 mstr
@ 2003-01-28 10:01 ` Richard Henderson
0 siblings, 0 replies; 2+ messages in thread
From: Richard Henderson @ 2003-01-28 10:01 UTC (permalink / raw)
To: mstr; +Cc: gcc
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~
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-01-28 6:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-26 22:00 REQ: naked attribute on x86 mstr
2003-01-28 10:01 ` Richard Henderson
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).