Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: DJ Delorie <dj@redhat.com>
Cc: ac131313@ges.redhat.com, binutils@sources.redhat.com,
	gdb@sources.redhat.com
Subject: Re: New binutils directory src/include/cpu/ for .cpu and .opc files?
Date: Thu, 12 Sep 2002 19:26:00 -0000	[thread overview]
Message-ID: <15745.19661.399094.489915@casey.transmeta.com> (raw)
In-Reply-To: <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.


  reply	other threads:[~2002-09-13  2:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12 18:10 Andrew Cagney
2002-09-12 18:43 ` DJ Delorie
2002-09-12 19:26   ` Doug Evans [this message]
2002-09-12 19:15 ` Hans-Peter Nilsson
2002-09-12 20:41   ` Andrew Cagney
2002-09-14  2:42     ` Hans-Peter Nilsson
2002-09-14  8:02       ` Doug Evans
2002-09-12 19:50 ` Ben Elliston
2002-09-12 20:16   ` Doug Evans
2002-09-12 21:19     ` DJ Delorie
2002-09-12 21:37       ` Doug Evans
2002-09-13  8:34     ` Frank Ch. Eigler
2002-09-26 17:04 ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15745.19661.399094.489915@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=ac131313@ges.redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox