This is the mail archive of the
crossgcc@cygnus.com
mailing list for the crossgcc project.
Re: underscore - coff vs. aout
- To: crossgcc@cygnus.com
- Subject: Re: underscore - coff vs. aout
- From: "Jacek M. Holeczek" <holeczek@us.edu.pl>
- Date: Wed, 14 Jul 1999 19:02:47 +0200 (MET DST)
- Reply-To: crossgcc@cygnus.com
Hi,
> > Man, that gcc.info stuff would be so useful if I knew how
I don't know which gcc.info part you need, but if it is the one about
"Controlling Names Used in Assembler Code", here it is :
========================================
You can specify the name to be used in the assembler code for a C
function or variable by writing the `asm' (or `__asm__') keyword after
the declarator as follows:
int foo asm ("myfoo") = 2;
This specifies that the name to be used for the variable `foo' in the
assembler code should be `myfoo' rather than the usual `_foo'.
On systems where an underscore is normally prepended to the name of
a C function or variable, this feature allows you to define names for
the linker that do not start with an underscore.
You cannot use `asm' in this way in a function *definition*; but you
can get the same effect by writing a declaration for the function
before its definition and putting `asm' there, like this:
extern func () asm ("FUNC");
func (x, y)
int x, y;
...
It is up to you to make sure that the assembler names you choose do
not conflict with any other assembler symbols. Also, you must not use a
register name; that would produce completely invalid assembler code.
GNU CC does not as yet have the ability to store static variables in
registers. Perhaps that will be added.
========================================
Jacek.
_______________________________________________
New CrossGCC FAQ: http://www.objsw.com/CrossGCC
_______________________________________________
To remove yourself from the crossgcc list, send
mail to crossgcc-request@cygnus.com with the
text 'unsubscribe' (without the quotes) in the
body of the message.