From: Mark Mitchell <mark@codesourcery.com>
To: NightStrike <nightstrike@gmail.com>
Cc: GCC <gcc@gcc.gnu.org>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Richard Guenther <rguenther@suse.de>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: End of GCC 4.6 Stage 1: October 27, 2010
Date: Sun, 05 Sep 2010 18:29:00 -0000 [thread overview]
Message-ID: <4C83E189.1030601@codesourcery.com> (raw)
In-Reply-To: <AANLkTimNk+fD9dAVByQZsjYoRCiHd2eLQUnpw=QKjy6T@mail.gmail.com>
On 9/5/2010 11:23 AM, NightStrike wrote:
>> It's not so much a matter of "checking off". It's a combination of the
>> SC's perception of the importance of the target and the technical stats
>> of the port. I can raise the issue with the SC, if you like, but,
>> personally, I'm not sure that 64-bit Windows is significant enough as a
>> target platform for GCC to merit that status.
>
> Ouch. What criteria do you use for that analysis?
I can't say what criteria the SC uses; I don't know what basis other SC
members use to decide.
I use my own instincts (which, I admit, is not a scientific basis) for
deciding. I spend much of my life talking to various stakeholders in
GCC, and so I have a reasonable feel for where people are presently
using GCC, and where they would like to use it. Thus far, I've
certainly heard of some interest in 64-bit Windows, but nowhere near as
much as 32-bit Windows or Cygwin.
I certainly don't mind raising the issue, if you want me to do that; I'm
happy to carry messages to the SC independent of my own opinions.
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
next prev parent reply other threads:[~2010-09-05 18:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 22:55 Mark Mitchell
2010-09-05 4:23 ` NightStrike
2010-09-05 18:03 ` Mark Mitchell
2010-09-05 18:23 ` NightStrike
2010-09-05 18:29 ` Mark Mitchell [this message]
2010-09-05 18:35 ` NightStrike
2010-09-05 18:40 ` Mark Mitchell
2010-09-05 22:10 ` Gerald Pfeifer
2010-09-05 22:18 ` Tobias Burnus
2010-09-06 9:22 ` Richard Guenther
2010-09-06 16:19 ` NightStrike
2010-09-06 16:21 ` Richard Guenther
2010-09-06 16:33 ` Tim Prince
2010-09-06 17:18 ` NightStrike
2010-09-06 17:24 ` Andrew Haley
2010-09-06 17:32 ` NightStrike
2010-09-20 23:23 ` NightStrike
2010-09-21 10:01 ` Jonathan Wakely
2010-09-21 15:09 ` NightStrike
2010-09-21 17:27 ` Dave Korn
2010-09-23 22:09 ` NightStrike
2010-10-08 15:56 ` NightStrike
2010-10-08 16:06 ` Jonathan Wakely
2010-10-08 16:10 ` Kai Tietz
2010-10-08 16:54 ` NightStrike
2010-10-08 18:04 ` Jonathan Wakely
2010-10-08 18:11 ` NightStrike
2010-10-09 1:40 ` Dave Korn
2011-02-24 17:05 ` NightStrike
2010-10-08 21:09 ` Richard Guenther
2010-10-08 21:14 ` NightStrike
2010-10-09 0:42 ` Richard Guenther
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=4C83E189.1030601@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=nightstrike@gmail.com \
--cc=rguenther@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).