This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: New binutils directory src/include/cpu/ for .cpu and .opc files?
- From: Doug Evans <dje at transmeta dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: ac131313 at ges dot redhat dot com, binutils at sources dot redhat dot com, gdb at sources dot redhat dot com
- Date: Thu, 12 Sep 2002 19:26:21 -0700 (PDT)
- Subject: Re: New binutils directory src/include/cpu/ for .cpu and .opc files?
- References: <3D813B07.4090401@ges.redhat.com><200209130143.g8D1hdg03001@greed.delorie.com>
DJ Delorie writes:
> > I'd like to propose a new directory:
> >
> > src/include/cpu/
> >
> > The directory would contain the CGEN .cpu and .opc input files used to
> > generate CGEN based binutils disassemblers, assemblers and (?)
> > relocations. GDB could also use these files when generating CGEN based
> > simulators.
>
> They aren't really include files, they're *source* files. Shouldn't
> they go in one of the source directories?
>
> I really don't think we want to go down the slippery slope of using
> include as a catch-all. Perhaps the opcodes directory would be a
> better choice?
I've always thought the .opc files should go in src/opcodes.
Similarily, I kinda think the opcodes file generators should
go in opcodes. After all, they're rather closely tied with
the rest of opcodes. They're also closely tied with cgen of course.
But application file generators should be able to go with the
application and not cgen. Otherwise writing new generators for
new applications becomes problematic ....
And, fwiw, I don't like putting the .cpu files in src/include either.