This is the mail archive of the
mailing list for the GCC project.
Re: Revised patch to remove integer output macros
- From: Richard Sandiford <rsandifo at redhat dot com>
- To: Hans-Peter Nilsson <hp at bitrange dot com>
- Cc: <gcc-patches at gcc dot gnu dot org>
- Date: 16 Dec 2001 13:18:09 +0000
- Subject: Re: Revised patch to remove integer output macros
- References: <Pine.BSF.email@example.com>
Hans-Peter Nilsson <firstname.lastname@example.org> writes:
> > mmix
> > Now uses ".byte" exclusively, instead of using "BYTE" for
> > some things and ".byte" for others.
> That's not really good. Now we lost compatibility with Knuth's
> mmixal assembler/linker for assembly generated from simple C
> code. C++ was hopelessly lost before too, but the generated
> assembly wasn't really readable anyway. :-)
OK, I'll use BYTE.
> With your patch, are numbers always emitted as decimal, or are
> there cases (for C code) where numbers are emitted as 0xNNNN?
> I ask because the "0xNNNN" syntax isn't allowed in mmixal
> syntax; it has to be decimal, or "#NNNN" for hex.
In that case I'll keep the ASM_OUTPUT_CHAR code for bytes.
The debugging output will also use this code, giving you the
"BYTE #<hex>" syntax there too.
I notice the dwarf code still uses .2byte, .4byte and .8byte. The
new hook should allow you to use things like "WYDE #<hex>" instead,
if that's appropriate.