From: Janis Johnson <janis187@us.ibm.com>
To: Arto Nirkko <arto.nirkko@insel.ch>
Cc: gcc@gcc.gnu.org
Subject: Re: gcc-3.1.1 bootstrap with -O3 -funroll-loops sucessful on sparc-sun-solaris2.6
Date: Mon, 12 Aug 2002 09:32:00 -0000 [thread overview]
Message-ID: <20020812093348.D1889@us.ibm.com> (raw)
In-Reply-To: <200208121026.MAA29049@neuro.insel.ch>
On Mon, Aug 12, 2002 at 12:26:56PM +0200, Arto Nirkko wrote:
>
> gcc-3.1.1 (all supported languages) bootstrapped fine
> as static build (--disable-shared, avoids problems with
> missing dynamic gcc libraries when compiled binaries
> are transferred to other non-build systems)
> with good optimization (-O3 -funroll-loops ...)
> on Solaris 2.6 using GNU as and ld from binutils-2.13.
Thanks! Your message is linked from the GCC 3.1 build status list at
http://gcc.gnu.org/gcc-3.1/buildstat.html .
Janis
prev parent reply other threads:[~2002-08-12 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 3:21 Arto Nirkko
2002-08-12 9:32 ` Janis Johnson [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=20020812093348.D1889@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=arto.nirkko@insel.ch \
--cc=gcc@gcc.gnu.org \
/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).