From: fche@redhat.com (Frank Ch. Eigler)
To: Doug Evans <dje@transmeta.com>
Cc: Ben Elliston <bje@redhat.com>,
binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: New binutils directory src/include/cpu/ for .cpu and .opc files?
Date: Fri, 13 Sep 2002 08:34:00 -0000 [thread overview]
Message-ID: <o5admlc390.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <15745.22648.285894.135472@casey.transmeta.com>
dje wrote:
> [...]
> How about src/cgen-cpu (*)? Or maybe even src/cpu/cgen.
If the idea of a new directory is just to separate (C)FSF from
non-(C)FSF CGEN input model files, then such a big hierarchy change is
not needed: e.g. src/cgen/fsf-cpu.
- FChE
next prev parent reply other threads:[~2002-09-13 15:34 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
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 [this message]
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=o5admlc390.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=bje@redhat.com \
--cc=dje@transmeta.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