From: fche@redhat.com (Frank Ch. Eigler)
To: cgen@sources.redhat.com
Subject: [gmane.comp.gnu.binutils,gmane.comp.gdb.devel] Re: [Fwd: Re: New binutils directory src/include/cpu/ for .cpu and .opc files?]
Date: Mon, 30 Sep 2002 08:40:00 -0000 [thread overview]
Message-ID: <o54rc7iiys.fsf@toenail.toronto.redhat.com> (raw)
Hi -
I wonder who will end up writing the necessary cgen changes to search
for model files in this additional input directory:
From: Nick Clifton <nickc@redhat.com>
Subject: Re: [Fwd: Re: New binutils directory src/include/cpu/ for .cpu and .opc files?]
Date: 30 Sep 2002 11:34:27 +0100
To: binutils@sources.redhat.com
Cc: gdb@sources.redhat.com
Hi Guys,
> From: Andrew Cagney <ac131313@redhat.com>
>
> It would appear that the first preference is src/cpu/. The runner up
> being src/opcodes/<something>/
>
> Nick?
And the winner is ... src/cpu/
So - I have added the directory to the top level of the binutils
directory hierarchy, added it to the binutils module (and created a
naked-cpu module) and applied this patch to Makefile.in so that it and
its contents should be included in any future binutils release.
If I have forgotten anything please let me know.
Cheers
Nick
2002-09-30 Nick Clifton <nickc@redhat.com>
* cpu: New top level directory. Intended to hold input files for
CGEN which have FSF copyright assignment.
* Makefile.in (BINUTILS_SUPPORT_DIRS): Add cpu directory.
reply other threads:[~2002-09-30 15:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=o54rc7iiys.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=cgen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).