This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: RFC: designated initializer vs. long long for i386 assembler
- From: Ian Lance Taylor <iant at google dot com>
- To: "H. J. Lu" <hjl at lucon dot org>
- Cc: Jan Beulich <jbeulich at novell dot com>, binutils at sourceware dot org
- Date: 13 Mar 2007 08:14:22 -0700
- Subject: Re: RFC: designated initializer vs. long long for i386 assembler
- References: <20070212155323.GA8495@lucon.org> <20070213232407.GB15831@bubble.grove.modra.org> <20070214001412.GA30144@lucon.org> <20070214015134.GA8541@bubble.grove.modra.org> <20070214020138.GA30518@lucon.org> <20070312190508.GA7845@lucon.org> <45F66D2D.76E4.0078.0@novell.com> <20070313124835.GA12145@lucon.org>
"H. J. Lu" <hjl@lucon.org> writes:
> The generated file, i386-inst.h, should be checked into CVS. People
> who change include/opcode/i386.h is responsible to regenerate
> i386-inst.h with the tool compiled with a C99 compiler. They are
> the only people who need a C99 compiler.
That sounds too complicated to me. If you're going to go that far,
just invent a syntax which lets you specify what you want, and write a
little tool which parses that syntax. Then you don't need to worry
about keeping the generated file up to date.
Or, simpler, just wrap every entry in i386.h in a macro
OP(name, bytes, val, ...)
and expand to
name, bytes, val, ..., (flags >> 32), (flags & 0xffff), ...
Of course it would be super nice to move the opcode table from
include/opcode/i386.h into opcodes/i386-opc.c.
Ian