public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
* [gmane.comp.gnu.binutils,gmane.comp.gdb.devel] Re: [Fwd: Re: New binutils directory src/include/cpu/ for .cpu and .opc files?]
@ 2002-09-30  8:40 Frank Ch. Eigler
  0 siblings, 0 replies; only message in thread
From: Frank Ch. Eigler @ 2002-09-30  8:40 UTC (permalink / raw)
  To: cgen


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.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2002-09-30 15:40 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-09-30  8:40 [gmane.comp.gnu.binutils,gmane.comp.gdb.devel] Re: [Fwd: Re: New binutils directory src/include/cpu/ for .cpu and .opc files?] Frank Ch. Eigler

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).