public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Bosscher <stevenb@suse.de>
To: Jonathan Wilson <jonwil@tpgi.com.au>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: what are the "primary targets" for GCC?
Date: Thu, 02 Dec 2004 12:57:00 -0000	[thread overview]
Message-ID: <7889542.1101992254266.SLOX.WebMail.wwwrun@extimap.suse.de> (raw)
In-Reply-To: <41AF09C3.4050504@tpgi.com.au>

On Dec 02, 2004 01:25 PM, Jonathan Wilson <jonwil@tpgi.com.au> wrote:

> I see lots of references to some targets being the "primary targets" (which 
> I assume means that those backends are the ones the GCC folk consider the 
> most important) but which targets are these?

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.

(Interesting nit: The criteria for GCC 3.4 are still only a draft
according to that page ;-)).

There are no documented GCC 4.0.0 Release Criteria yet, and I don't
know who is responsible for proposing the criteria and approving them.
Until somebody proposes something I suppose the "primary targets" are
just those which are the most important historically or from the point
of view of the majority of the contributors (x86*-linux, MIPS, HPPA,
powerpc*, HPPA, maybe Alpha, maybe ARM, at least one *BSD target, ...).

Gr.
Steven

  parent reply	other threads:[~2004-12-02 12:57 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 [this message]
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
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=7889542.1101992254266.SLOX.WebMail.wwwrun@extimap.suse.de \
    --to=stevenb@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=jonwil@tpgi.com.au \
    /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).