[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: x86 and PowerPC ABIs and Calling Conventions
- To: tech_(_at_)_openbsd_(_dot_)_org
- Subject: Re: x86 and PowerPC ABIs and Calling Conventions
- From: Marc Espie <Marc_(_dot_)_Espie_(_at_)_liafa_(_dot_)_jussieu_(_dot_)_fr>
- Date: Sun, 29 Nov 1998 14:02:57 +0100
On Sun, Nov 29, 1998 at 01:43:52PM +0100, Felix Schroeter wrote:
> On Wed, Nov 11, 1998 at 05:03:51AM -0500, Nathan Binkert wrote:
> > Also, if anyone has a pointer where I can find out how the __asm__
> > directive works, I would appreciate that as well.
> Either compile your assembler parts as separate sources (foo.s, or foo.S
> the latter gets preprocessed with cpp). Or look at the gcc info pages,
> go to "C Extensions", "Extended Asm".
Be VERY careful about what's documented there, and what's not. In case you
get into `undocumented behavior', especially with respect to clobberred
registers, you're almost sure to set yourself up for trouble later.
That's what happened to linux, and that's why there was a shitload of
cleaning up to be able to compile the kernel under anything newer than
In case of doubt, get yourself onto the egcs ml and ASK.
Part of the behavior/internals of gcc/egcs is still not documented. Some of
it won't change, some is changing, and is bound to change in the future.
|anime, sf, juggling, unicycle, acrobatics, comics...
|AmigaOS, OpenBSD, C++, perl, Icon, PostScript...
| `real programmers don't die, they just get out of beta'
Visit your host, monkey.org