From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: dclarke@blastwave.org, gcc@gcc.gnu.org
Subject: Re: # of unexpected failures 768 ?
Date: Mon, 31 Oct 2011 22:33:00 -0000 [thread overview]
Message-ID: <CAH6eHdSZW7Ke85crSX+Fnb6LmGaPzoFHUvhcwsPBs2sBrfnssg@mail.gmail.com> (raw)
In-Reply-To: <yddty6p9i4n.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
On 31 October 2011 17:38, Rainer Orth wrote:
> Dennis Clarke <dclarke@blastwave.org> writes:
>
>>>> I'm uncertain if Solaris 8/x86 still supports bare i386 machines, so it
>>>> might be better to keep the default of pentiumpro instead.
>>>
>>> Solaris 8 won't run on anything less than pentium, I recently
>>> convinced someone else to stop building GCC for i386 on Solaris:
>>>
>>> http://gcc.gnu.org/ml/gcc-help/2011-10/msg00005.html
>>
>> The Os is on Vintage support until March 2012. Also, I never had problems
>
> That's not the question (but one reason why Solaris 8 support will be
> removed after GCC 4.7). As Jonathan documented, you can't run S8 on a
> bare 80386, so there's no reason the default code generation to that CPU.
Quite. In fact there are *very* good reasons not to configure for
80386: libstdc++'s configure uses the default arch being configured
for, and disables a number of features on i386 because it doesn't
support the required atomic ops.
So by configuring for i386 you will distribute a GCC package that is
missing useful features, but supports an ancient architecture that
Solaris doesn't even run on.
You should configure for pentium-pc-solaris2.8 or use --with-arch-32=pentium
next prev parent reply other threads:[~2011-10-31 18:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 18:49 Dennis Clarke
2011-10-31 19:07 ` Rainer Orth
2011-10-31 22:33 ` Jonathan Wakely [this message]
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
-- 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-03 15:32 Dennis Clarke
2011-11-02 18:29 Dennis Clarke
2011-11-02 14:29 Dennis Clarke
2011-11-02 11:26 Dennis Clarke
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=CAH6eHdSZW7Ke85crSX+Fnb6LmGaPzoFHUvhcwsPBs2sBrfnssg@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=dclarke@blastwave.org \
--cc=gcc@gcc.gnu.org \
--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).