From: Marc Glisse <marc.glisse@inria.fr>
To: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
Cc: Dennis Clarke <dclarke@blastwave.org>,
Ian Lance Taylor <iant@google.com>,
gcc-help@gcc.gnu.org, ebotcazou@adacore.com,
jwakely.gcc@gmail.com
Subject: Re: the struggle for a 64-bit GCC on Solaris 10 - part 2
Date: Mon, 12 Nov 2012 21:29:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1211122218430.4738@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <50A16762.7050202@cs.utoronto.ca>
On Mon, 12 Nov 2012, Ryan Johnson wrote:
> I'm still really unclear on why you're having so much trouble with this. Have
> you tried bootstrapping with SunCC like I did?
I assume you mean suncc. gcc's code contains some C++ bugs that mean
that Oracle's C++ compiler won't compile it (a bit of an issue for 4.8).
--
Marc Glisse
next prev parent reply other threads:[~2012-11-12 21:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 16:10 Dennis Clarke
2012-11-12 16:53 ` Ryan Johnson
2012-11-12 17:09 ` Dennis Clarke
2012-11-12 17:54 ` Ian Lance Taylor
2012-11-12 21:00 ` Dennis Clarke
2012-11-12 21:17 ` Ryan Johnson
2012-11-12 21:20 ` Dennis Clarke
2012-11-12 21:26 ` Jonathan Wakely
2012-11-12 21:33 ` Dennis Clarke
2012-11-12 21:41 ` Ryan Johnson
2012-11-12 21:57 ` Dennis Clarke
2012-11-12 22:13 ` Jonathan Wakely
2012-11-12 22:22 ` Dennis Clarke
2012-11-12 22:32 ` Jonathan Wakely
2012-11-12 22:37 ` Dennis Clarke
2012-11-12 22:49 ` Jonathan Wakely
2012-11-12 22:49 ` Jonathan Wakely
2012-11-12 22:55 ` Dennis Clarke
2012-11-12 23:26 ` Jonathan Wakely
2012-11-15 1:01 ` Dennis Clarke
2012-11-12 23:04 ` Dennis Clarke
2012-11-12 23:17 ` Ryan Johnson
2012-11-12 23:19 ` Dennis Clarke
2012-11-12 23:15 ` Ryan Johnson
2012-11-12 23:17 ` Dennis Clarke
2012-11-12 23:25 ` Ryan Johnson
2012-11-12 21:29 ` Marc Glisse [this message]
2012-11-12 21:34 ` Ryan Johnson
2012-11-12 21:36 ` Dennis Clarke
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=alpine.DEB.2.02.1211122218430.4738@laptop-mg.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=dclarke@blastwave.org \
--cc=ebotcazou@adacore.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
--cc=jwakely.gcc@gmail.com \
--cc=ryan.johnson@cs.utoronto.ca \
/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).