public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/43733] bootstrap fails on Solaris 10 x86 with GNU as 2.15 and --with-arch=core2
Date: Wed, 28 Apr 2010 18:38:00 -0000 [thread overview]
Message-ID: <20100428183804.7460.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43733-16379@http.gcc.gnu.org/bugzilla/>
------- Comment #23 from redi at gcc dot gnu dot org 2010-04-28 18:38 -------
core2 works fine for bi-arch linux builds, but I'll try your suggestion on
Solaris asap
I assume it will work, but 64bit code will not use the core2 instructions,
which might be suboptimal (I want to use the cpu to the full potential!)
I imagine it's also possible for the same problem to occur using -march=native,
if the processor flags indicate core2 instructions will work.
That said, 2.15 is an ancient gas (even though it's very common on Solaris 10)
so I'm not too worried about this bug being fixed and I agree it's not worth
changing the config docs.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43733
next prev parent reply other threads:[~2010-04-28 18:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 16:43 [Bug bootstrap/43733] New: bootstrap fails building libgfortran on Solaris x86 with GNU as redi at gcc dot gnu dot org
2010-04-12 16:51 ` [Bug bootstrap/43733] " redi at gcc dot gnu dot org
2010-04-12 17:12 ` ubizjak at gmail dot com
2010-04-12 17:15 ` redi at gcc dot gnu dot org
2010-04-12 17:16 ` redi at gcc dot gnu dot org
2010-04-12 17:24 ` [Bug libfortran/43733] " ubizjak at gmail dot com
2010-04-12 17:25 ` redi at gcc dot gnu dot org
2010-04-12 17:30 ` redi at gcc dot gnu dot org
2010-04-12 17:48 ` ubizjak at gmail dot com
2010-04-12 17:56 ` ubizjak at gmail dot com
2010-04-12 17:57 ` ubizjak at gmail dot com
2010-04-12 18:02 ` redi at gcc dot gnu dot org
2010-04-12 18:05 ` redi at gcc dot gnu dot org
2010-04-12 18:09 ` redi at gcc dot gnu dot org
2010-04-12 18:16 ` ubizjak at gmail dot com
2010-04-12 18:21 ` redi at gcc dot gnu dot org
2010-04-12 18:42 ` [Bug bootstrap/43733] " ubizjak at gmail dot com
2010-04-12 20:03 ` ubizjak at gmail dot com
2010-04-13 9:22 ` [Bug libfortran/43733] " redi at gcc dot gnu dot org
2010-04-13 10:12 ` burnus at gcc dot gnu dot org
2010-04-13 11:21 ` [Bug bootstrap/43733] " redi at gcc dot gnu dot org
2010-04-13 12:26 ` [Bug bootstrap/43733] bootstrap fails on Solaris 10 x86 with GNU as 2.15 and --with-arch=core2 redi at gcc dot gnu dot org
2010-04-28 18:14 ` ro at gcc dot gnu dot org
2010-04-28 18:38 ` redi at gcc dot gnu dot org [this message]
2010-05-19 6:47 ` ubizjak at gmail dot com
2010-05-19 12:22 ` ubizjak at gmail dot com
2010-05-20 10:19 ` redi at gcc dot gnu dot org
2010-05-20 18:52 ` uros at gcc dot gnu dot org
2010-05-20 18:53 ` [Bug target/43733] " ubizjak at gmail dot com
2010-05-24 16:23 ` uros at gcc dot gnu dot org
2010-05-24 16:27 ` uros at gcc dot gnu dot org
2010-05-24 16:29 ` uros at gcc dot gnu dot org
2010-05-24 16:31 ` ubizjak at gmail dot com
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=20100428183804.7460.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).