public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Doug Evans <dje@sebabeach.org>
Cc: fche@redhat.com, cgen@sourceware.org
Subject: Re: remove dups from cgen/cpu?
Date: Fri, 24 Jul 2009 17:53:00 -0000	[thread overview]
Message-ID: <4A69F804.1020107@gmail.com> (raw)
In-Reply-To: <20090709160851.B60D36E3D1@sebabeach.org>

[-- Attachment #1: Type: text/plain, Size: 379 bytes --]

Doug Evans wrote:
> Hi.
> 
> I think it's time to remove the duplicates in src/cgen/cpu
> and keep just the copies in src/cpu.
> 
> Any objections?

  None here, but how about doing this while we're at it?

cgen/ChangeLog:

	* Makefile.am (ARCHFILE): Search both cpu/ subdirs, with priority
	to top-level cpu/ over cgen/cpu/.
	* Makefile.in: Regenerate.

    cheers,
      DaveK

[-- Attachment #2: cgen-which-cpu-dir.diff --]
[-- Type: text/x-c, Size: 669 bytes --]

Index: cgen/Makefile.am
===================================================================
RCS file: /cvs/src/src/cgen/Makefile.am,v
retrieving revision 1.8
diff -p -u -r1.8 Makefile.am
--- cgen/Makefile.am	13 Jul 2009 20:55:21 -0000	1.8
+++ cgen/Makefile.am	24 Jul 2009 17:46:39 -0000
@@ -7,7 +7,7 @@ SUBDIRS = doc testsuite
 GUILE = "`if test -f ../guile/libguile/guile ; then echo ../guile/libguile/guile; else echo guile ; fi`" -l $(srcdir)/guile.scm -s
 CGENFLAGS = -v
 ARCH = @arch@
-ARCHFILE = $(srcroot)/cpu/$(ARCH).cpu
+ARCHFILE = $(firstword $(wildcard $(srcroot)/cpu/$(ARCH).cpu $(srcroot)/cgen/cpu/$(ARCH).cpu))
 
 # for various utility rules
 MACHS = all

      parent reply	other threads:[~2009-07-24 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 16:09 Doug Evans
2009-07-09 17:03 ` Dave Brolley
2009-07-12 16:07   ` Doug Evans
2009-07-24 17:53 ` Dave Korn [this message]

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=4A69F804.1020107@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=cgen@sourceware.org \
    --cc=dje@sebabeach.org \
    --cc=fche@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).