From: Dennis Clarke <dclarke@blastwave.org>
To: Ian Lance Taylor <iant@google.com>
Cc: Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Michael Haubenwallner <michael.haubenwallner@salomon.at>,
gcc@gcc.gnu.org
Subject: Re: # of unexpected failures 768 ?
Date: Thu, 03 Nov 2011 15:32:00 -0000 [thread overview]
Message-ID: <59839.10.0.66.17.1320334339.squirrel@interact.purplecow.org> (raw)
> Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
>
>> Ian Lance Taylor <iant@google.com> writes:
>>
>>> Michael Haubenwallner <michael.haubenwallner@salomon.at> writes:
>>>
>>>> But still: given that x86-solaris started with some Pentium, I just
>>>> can't believe gcc can "optimize" for real 80386 CPU on Solaris now.
>>>>
>>>> Especially as i386 (from config.guess) is the default too.
>>>
>>> I'm not sure why you don't believe it. It is what I would expect.
>>>
>>> If we want to make this work more normally for ordinary users, I think
>>> the right thing to do would be to patch config.guess to compute a
>>> better
>>> value for the build system CPU on Solaris systems.
>>
>> Please no: alpha went this route, and the consequence is that your
>> self-built gcc will generate code for the build system. This breaks
>> completely if you have a heterogeneous collection of systems, and the
>> GCC build system isn't the least common denominator of them. This
>> single-system mindset creates unnecessary trouble in this scenario.
>> GCC's configure has enough control over the default target CPU, even
>> without messing with config.guess, and most other programs won't care
>> about this at all.
>
> Oh, I completely agree that it would be wrong to have config.guess
> produce the exact CPU used on the build system.
>
> But having config.guess produce "i386" for an OS which does not even run
> on a vanilla i386 is also wrong. A much better choice here would be the
> earliest CPU value which the OS actually supports.
$ isalist -v
pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
I would suggest pentium_pro if one can still find one running out there.
Dennis
--
--
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x1D936C72FA35B44B
+-------------------------+-----------------------------------+
| Dennis Clarke | Solaris and Linux and Open Source |
| dclarke@blastwave.org | Respect for open standards. |
+-------------------------+-----------------------------------+
next reply other threads:[~2011-11-03 15:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 15:32 Dennis Clarke [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-07 18:03 Dennis Clarke
2011-11-07 2:14 Dennis Clarke
2011-11-07 7:31 ` Ian Lance Taylor
2011-11-02 18:29 Dennis Clarke
2011-11-02 14:29 Dennis Clarke
2011-11-02 11:26 Dennis Clarke
2011-10-31 18:49 Dennis Clarke
2011-10-31 19:07 ` Rainer Orth
2011-10-31 22:33 ` Jonathan Wakely
2011-11-02 6:52 ` Michael Haubenwallner
2011-11-02 11:41 ` Jonathan Wakely
2011-11-02 13:53 ` Michael Haubenwallner
2011-11-02 17:11 ` Jonathan Wakely
2011-11-02 17:42 ` Michael Haubenwallner
2011-11-02 18:07 ` Rainer Orth
2011-11-02 19:55 ` Michael Haubenwallner
2011-11-02 18:10 ` Ian Lance Taylor
2011-11-02 18:15 ` Rainer Orth
2011-11-02 18:21 ` Ian Lance Taylor
2011-10-31 9:28 Dennis Clarke
2011-10-31 16:15 ` Eric Botcazou
2011-10-31 17:22 ` Rainer Orth
2011-10-31 18:21 ` Jonathan Wakely
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=59839.10.0.66.17.1320334339.squirrel@interact.purplecow.org \
--to=dclarke@blastwave.org \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=michael.haubenwallner@salomon.at \
--cc=ro@cebitec.uni-bielefeld.de \
/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).