From: Mark Mitchell <mark@codesourcery.com>
To: "guerby@acm.org" <guerby@acm.org>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC 3.1
Date: Mon, 08 Oct 2001 15:01:00 -0000 [thread overview]
Message-ID: <98930000.1002578389@gandalf.codesourcery.com> (raw)
In-Reply-To: <200110082035.f98KZcE04530@ulmo.localdomain>
--On Monday, October 08, 2001 10:35:38 PM +0200 "guerby@acm.org"
<guerby@acm.org> wrote:
>> That is the cutoff date for major new functionality (new programming
>> languages, new optimization passes, etc.) in GCC 3.1.
>
> I assume that for Ada new supported targets are ok? I'm thinking about
> support of the BSD family, GNU/Linux on non x86, and may be MacOS X
> that I hope will be contributed now that the sources are available to
> everyone to play with.
In general, I think new ports are an exception. (After all, we added
the S/390 port to GCC 3.0.1.) The reason is that those changes were
unbelievably unlikely to impact anything else.
So, yes, adding configury bits for Ada, especially during the "minor
improvements" phase, is welcome.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2001-10-08 15:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 13:27 Mark Mitchell
2001-10-08 13:35 ` guerby
2001-10-08 15:01 ` Mark Mitchell [this message]
2001-10-08 17:56 ` Carlo Wood
2001-10-08 21:00 ` Daniel Berlin
-- strict thread matches above, loose matches on Subject: below --
2002-07-21 15:25 gcc 3.1 lartey
2002-07-21 15:25 ` Paolo Carlini
2002-07-22 13:26 ` lartey
2002-07-09 0:23 lartey
2002-05-23 8:20 GCC 3.1 James Whitelaw
2002-05-10 0:53 Mark Mitchell
2002-04-19 2:32 David Rasmussen
2002-04-19 2:33 ` Gerald Pfeifer
2002-04-19 2:57 ` David Rasmussen
2002-04-19 3:05 ` Jakub Jelinek
2002-04-19 3:19 ` Paolo Carlini
2002-04-19 3:24 ` Hans-Peter Nilsson
2001-10-09 18:05 Robert Schweikert
2001-10-09 18:14 ` Mark Mitchell
2001-10-09 18:17 ` DJ Delorie
2001-10-01 9:30 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=98930000.1002578389@gandalf.codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=guerby@acm.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).