public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mrs@apple.com>
To: Giovanni Bajo <rasky@develer.com>
Cc: Steven Bosscher <stevenb@suse.de>, gcc@gcc.gnu.org
Subject: Re: what are the "primary targets" for GCC?
Date: Thu, 02 Dec 2004 19:55:00 -0000	[thread overview]
Message-ID: <A5568C4C-13E6-4BE3-9D19-151E431F5921@apple.com> (raw)
In-Reply-To: <033f01c4d873$e969f310$f503030a@mimas>

On Dec 2, 2004, at 5:36 AM, Giovanni Bajo wrote:
> I asked the SC a clarification on the release criteria for 4.x here:
> http://gcc.gnu.org/ml/gcc/2004-10/msg01229.html
>
> but got no answer.

I don't feel they have to answer these questions.  If they feel any 
specific one is compelling to them, they should of course state a 
direction for us to move in; otherwise, the answers to your questions 
can be a consensus view of the people doing the work in gcc combined 
with what work people sign up to actually do.  Someone can propose 
numbers and criteria and solicit feedback.  The RM has the latitude to 
push us in that direction, or this one and to publish any such list as 
he sees fit.


For example, I propose that we consider Darwin a primary platform.  
This isn't crucial or critical, but, I think reflects reality better.

I propose that 25% speed regressions at -O0 are beyond what we consider 
ok.  I think we can conservatively say that 4% might be more reasonable 
and reflective of the current climate.

  parent reply	other threads:[~2004-12-02 19:55 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 [this message]
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=A5568C4C-13E6-4BE3-9D19-151E431F5921@apple.com \
    --to=mrs@apple.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rasky@develer.com \
    --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).