public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/39150] Configure scripts have no 64-Bit Solaris defined (only i386-solaris*).
Date: Thu, 12 Feb 2009 13:36:00 -0000 [thread overview]
Message-ID: <20090212133610.4108.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39150-13830@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from rob1weld at aol dot com 2009-02-12 13:36 -------
(In reply to comment #1)
> How is this major, this is an enhancement to the build system. i386-solaris is
> a multi arch target so it includes the x86_64 solaris target also.
It could be called an "enhancement to the build system".
I call it a "fault of the build system" and a subsequent "fault of the
test system" in that this Operating System has 2 ABIs and much of gcc
seems to rely on 'uname' to determine the HTB, that is a mistake.
The correct manner for gcc to decide that the HOST is the so-called
"x86_64-pc-solaris2.11" host is to correctly query the Boot Mode.
That is something that gcc does not do correctly on this Platform.
I do not know that it is an "enhancement" that this Platform should
build and test in the the same manner as other Platforms. I call it
a major Bug. I guess it is a matter of semantics.
Rob
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39150
next prev parent reply other threads:[~2009-02-12 13:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 4:14 [Bug bootstrap/39150] New: " rob1weld at aol dot com
2009-02-11 20:56 ` [Bug bootstrap/39150] " pinskia at gcc dot gnu dot org
2009-02-12 13:36 ` rob1weld at aol dot com [this message]
2009-02-13 8:37 ` rob1weld at aol dot com
2009-02-13 9:12 ` rob1weld at aol dot com
2009-02-16 13:12 ` rob1weld at aol dot com
2009-10-23 12:13 ` grobian at gentoo dot org
2010-04-28 19:55 ` ro at gcc dot gnu dot org
2010-04-28 19:56 ` ro at gcc dot gnu dot org
2010-04-28 20:55 ` ro at gcc dot gnu dot org
2010-04-28 22:10 ` ebotcazou at gcc dot gnu dot org
2010-04-28 22:18 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-05-04 7:21 ` rob1weld at aol dot com
2010-05-06 19:27 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-05-06 19:54 ` ebotcazou at gcc dot gnu dot org
2010-05-17 2:34 ` rob1weld at aol dot com
2010-07-20 19:02 ` rob1weld at aol dot com
2010-07-20 19:21 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-07-21 23:17 ` rob1weld at aol dot com
2010-07-22 11:50 ` rob1weld at aol dot com
2010-08-30 16:36 ` rwild at gcc dot gnu dot org
[not found] <bug-39150-4@http.gcc.gnu.org/bugzilla/>
2011-07-06 11:38 ` ro at gcc dot gnu.org
2011-07-07 9:26 ` ro at gcc dot gnu.org
2011-07-07 10:02 ` ro at gcc dot gnu.org
2011-07-18 16:40 ` ro at gcc dot gnu.org
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=20090212133610.4108.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).