From: Ian Lance Taylor <ian@airs.com>
To: Steve Munroe <sjmunroe@us.ibm.com>
Cc: libc-alpha@sources.redhat.com, gcc@gcc.gnu.com,
binutils@sourceware.org, autoconf@gnu.org,
Roland McGrath <roland@redhat.com>
Subject: Re: [RFC] Additional targets for powerpc
Date: Thu, 22 Sep 2005 22:57:00 -0000 [thread overview]
Message-ID: <m3wtl8n2uw.fsf@gossamer.airs.com> (raw)
In-Reply-To: <OF11BDA2D0.E99C10BD-ON86257084.0077BF90-86257084.007AFAC3@us.ibm.com>
Steve Munroe <sjmunroe@us.ibm.com> writes:
> Retain (compatible with all existing Linux on Power systems)
> powerpc (a synonym for powerpc32)
> powerpc32
> powerpc64
> And add
> power4_32
> power4_64
> power5_32
> power5_64
> ppc970_32
> ppc970_64
> Or alternatively
> powerpc32_power4
> powerpc64_power4
> powerpc32_power5
> powerpc64_power5
> powerpc32_970
> powerpc64_970 I see no need to support a separate (from existing
> powerpc32/64) POWER3 and RS64IV targets at this time. The POWER3 systems
> are quite old and the RS64IV systems are "strongly storage consistent"
> machines. The POWER4, POWER5, and PPC970 processors allow "weak storage
> consistency" and are more aggressively piped for out-of-order instruction
> execution. This is difference requires very different instruction
> scheduling for optimal performance.
> Glibc and other package changes
>
> The changes needed to enable additional targets for glibc include:
>
> * Add the new machine targets to ./scripts/config.sub (and in autoconf)
I think we've found with the i386 and, especially, the MIPS, that this
approach is unwieldy and becomes confusing. Have you considered using
the --with-cpu, --with-arch and --with-tune configure options, instead
of adding a slew of CPU names? I don't know much about glibc
configury, but those options suffice for gcc and the binutils.
The main drawback at present is that there is no way to map from
config.guess to --with-cpu. But I believe that is a solvable problem.
(If people need to support compilers with different default targets on
the same system, they can use --program-prefix.)
Ian
next prev parent reply other threads:[~2005-09-22 22:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 22:44 Steve Munroe
2005-09-22 22:57 ` Ian Lance Taylor [this message]
2005-09-22 23:01 ` Roland McGrath
2005-09-22 23:01 ` Daniel Jacobowitz
2005-09-22 23:06 ` Ian Lance Taylor
2005-09-23 0:35 ` Doug Evans
2005-09-23 10:28 ` Roland McGrath
2005-09-22 23:02 ` Ian Lance Taylor
2005-09-23 5:20 ` Doug Evans
2005-09-22 22:58 ` Paul Brook
2005-09-22 23:00 ` Paul Brook
2005-09-23 15:29 ` Kumar Gala
2005-09-23 16:38 ` Steve Munroe
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=m3wtl8n2uw.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=autoconf@gnu.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.com \
--cc=libc-alpha@sources.redhat.com \
--cc=roland@redhat.com \
--cc=sjmunroe@us.ibm.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).