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

From: Roland McGrath <roland@redhat.com>
Date: Fri, 24 Feb 2006 17:08:23 -0800 (PST)

> > I've sent a patch for scripts/config.sub to config-patches the other
> > day, so that part of adding sparcv9v and sparc64v should show up
> > eventually.
> 
> As a rule we don't put in new configuration support until the canonical
> config.sub groks it.

config.sub really puts an unreasonable monkey wrench into the works
for doing development of new build targets for any GNU package.

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.

> > This adds the "sparcv9v-*" and "sparc64v-*" build targets, the
> > optimized memcpy/memset for that platform, and the necessary Implies
> > files.
> 
> I think this would be better done without Implies files.  Just use
> machine=sparc/sparc32/sparcv9/sparcv9v and the right things should happen.

Will that actually work?

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

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

  reply	other threads:[~2006-02-25  1:29 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 [this message]
2006-02-25  1:45     ` Roland McGrath

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=20060224.172917.09191154.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=libc-hacker@sources.redhat.com \
    --cc=roland@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).