From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: gcc@gcc.gnu.org
Subject: Re: gcc -m64 for Solaris10 x86
Date: Tue, 14 Dec 2004 12:34:00 -0000 [thread overview]
Message-ID: <yddu0qpt5wh.fsf@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: Albert Chin's message of "Mon, 13 Dec 2004 16:08:43 -0600"
Albert Chin <gcc@mlists.thewrittenword.com> writes:
> So GCC on Solaris 10/x86 will require GNU as? Why isn't
> /usr/ccs/bin/as good enough?
Some uses are just artifacts of the initial port than can easily be
avoided. See the thread starting at
http://gcc.gnu.org/ml/gcc-patches/2004-11/msg00908.html
for an initial attempt to use Sun as instead. I haven't found time yet to
further work on the open issues.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
next prev parent reply other threads:[~2004-12-14 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 12:55 Guenter Feldmann
2004-12-13 16:11 ` Daniel Jacobowitz
2004-12-13 17:16 ` Rainer Orth
2004-12-13 22:08 ` Albert Chin
2004-12-14 12:34 ` Rainer Orth [this message]
2004-12-14 18:26 ` Mark Mitchell
2004-12-15 18:44 ` Rainer Orth
2004-12-15 19:00 ` Mark Mitchell
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=yddu0qpt5wh.fsf@xayide.TechFak.Uni-Bielefeld.DE \
--to=ro@techfak.uni-bielefeld.de \
--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).