From: Jonathan Wilson <jonwil@tpgi.com.au>
To: Steven Bosscher <stevenb@suse.de>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: what are the "primary targets" for GCC?
Date: Thu, 02 Dec 2004 14:01:00 -0000 [thread overview]
Message-ID: <41AF20F8.1010408@tpgi.com.au> (raw)
In-Reply-To: <7889542.1101992254266.SLOX.WebMail.wwwrun@extimap.suse.de>
> That depends from release to release. For GCC 3.4 you can find the
> list on http://gcc.gnu.org/gcc-3.4/criteria.html under the header
> "Platform Support". Same for GCC 3.3 and earlier.
ok, that page seems like what I want.
The only noted difference between 3.3 and 3.4 seems to be the AIX target
which has been bumped up for 3.4 (presumably because a new version of AIX
appeared)
I wonder why apple (i.e. OSX/darwin) is not a primary platform for GCC
(given that GCC is the primary compiler for that plaform).
I guess it is because apple keeps a local branch of GCC with all sorts of
apple fixes in them.
Personally, I would love to see the win32 GCC (mingw) target be given a
higher priority (although that would rely on the mingw team being more
perpared to keep things going) as this target is (AFAIK) the best currently
available option as far as a free as in speech compiler for the windows
platform goes.
next prev parent reply other threads:[~2004-12-02 14:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 12:22 Jonathan Wilson
2004-12-02 12:54 ` Paolo Carlini
2004-12-02 12:58 ` Paolo Carlini
2004-12-02 12:57 ` Steven Bosscher
2004-12-02 13:37 ` Giovanni Bajo
2004-12-02 17:16 ` Joe Buck
2004-12-02 17:52 ` Gerald Pfeifer
2004-12-02 19:55 ` Mike Stump
2004-12-02 22:46 ` Joe Buck
2004-12-02 14:01 ` Jonathan Wilson [this message]
2004-12-02 17:15 ` Joe Buck
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=41AF20F8.1010408@tpgi.com.au \
--to=jonwil@tpgi.com.au \
--cc=gcc@gcc.gnu.org \
--cc=stevenb@suse.de \
/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).