public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: libc-hacker@sources.redhat.com
Subject: Re: [PATCH]: Sparc SUN4V Niagara optimize memset/memcpy
Date: Sat, 25 Feb 2006 01:45:00 -0000	[thread overview]
Message-ID: <20060225014529.7330B180A66@magilla.sf.frob.com> (raw)
In-Reply-To: David S. Miller's message of  Friday, 24 February 2006 17:29:17 -0800 <20060224.172917.09191154.davem@davemloft.net>

> It ususally takes about a week for a config.sub patch get handled,
> integrated, and propagated into the necessary trees.  Nothing impedes
> forward progress quite like this thing.

Sorry.  I take them as soon as it's agreed to by config-patches.

> I thought "machine=" takes a file path name, not a list of compatible
> targets.  For example:

It's a directory name, not a list, yes.  But all directories always imply
their parents.
 
> sparcv8plus | sparcv8plusa | sparcv9)
> 		base_machine=sparc machine=sparc/sparc32/sparcv9 ;;
> 
> I read that as meaning: search ${foo}/sparc/sparc32/sparcv9, else
> ${foo}/sparc/sparc32, else ${foo}/sparc

Try --enable-debug-configure.  The sysdeps directory list is an ordered
list of many directories.  That gets */sparc/sparc32/sparcv9 if it exists,
followed by */sparc/sparc32 if it exists, followed by */sparc if it exists.
Since something can't exist without its containing directory existing too,
you'll always get a trailing subset of that list.


Thanks,
Roland

      reply	other threads:[~2006-02-25  1:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 23:46 David S. Miller
2006-02-25  1:08 ` Roland McGrath
2006-02-25  1:29   ` David S. Miller
2006-02-25  1:45     ` Roland McGrath [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=20060225014529.7330B180A66@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=davem@davemloft.net \
    --cc=libc-hacker@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).