This is the mail archive of the
mailing list for the GCC project.
Re: Revised patch to remove integer output macros
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Richard Sandiford <rsandifo at redhat dot com>
- Cc: <gcc-patches at gcc dot gnu dot org>
- Date: Sun, 16 Dec 2001 00:30:04 -0500 (EST)
- Subject: Re: Revised patch to remove integer output macros
On 14 Dec 2001, Richard Sandiford wrote:
> I know of three cases where things genuinely changed:
> This target uses the same ops for unaligned and aligned data.
> It used to use ".quad" for unaligned data but not aligned data
> It will now use ".quad" for both.
Before, it seems it'd be split up in two ".dword":s.
> 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. :-)
I'll have to check whether using BYTE consistently is possible.
It has some constrained syntax and semantics.
Can't you have two different byte-size asm directives, default
the same? Perhaps I get the same effect through the new target
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.
I guess I'll find out.