From: Mark Mitchell <mark@codesourcery.com>
To: Aldy Hernandez <aldyh@redhat.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC 3.1 Branch
Date: Fri, 17 May 2002 00:21:00 -0000 [thread overview]
Message-ID: <40370000.1021615442@gandalf.codesourcery.com> (raw)
In-Reply-To: <20020517053114.GB19037@redhat.com>
--On Friday, May 17, 2002 03:31:14 PM +1000 Aldy Hernandez
<aldyh@redhat.com> wrote:
> On Fri, May 17, 2002 at 12:12:37AM -0400, Daniel Jacobowitz wrote:
>> On Fri, May 17, 2002 at 11:56:52AM +1000, Aldy Hernandez wrote:
>> > >>>>> "Mark" == Mark Mitchell <mark@codesourcery.com> writes:
>> >
>> > > c) they add support for new platforms, language features, etc.
>> > > that we did not support before -- and that we cannot,
>> > > therefore, be regressing.
>> >
>> > Great. I'd like permission to check in my cleanups to the user level
>> > include file: <altivec.h>
>> >
>> > There are some major fixes without which, altivec support isn't going
>> > to be very useful.
>>
>> Are you considering backporting the more important backend changes,
>> also? I don't know how practical it is, but lots of people would
>> appreciate it.
>
> hmm, i'm afraid mark said no.
Unless they fix regressions, I'm not inclined to take the risk. Tweaking
back ends is a very easy way to introduce subtle code-gen bugs.
Of course, that's not a hard and fast rule.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-05-17 6:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 18:48 Mark Mitchell
2002-05-16 21:07 ` Aldy Hernandez
2002-05-16 23:02 ` Daniel Jacobowitz
2002-05-16 23:09 ` Aldy Hernandez
2002-05-17 0:21 ` Mark Mitchell [this message]
2002-05-16 23:35 ` Mark Mitchell
2002-05-17 0:34 ` Aldy Hernandez
2002-05-17 1:21 ` Mark Mitchell
-- strict thread matches above, loose matches on Subject: below --
2002-02-26 0:40 Mark Mitchell
2002-02-26 8:25 ` Corey Minyard
2002-02-26 9:45 ` Mark Mitchell
2002-02-21 18:29 Richard Kenner
2002-02-21 19:03 ` David Edelsohn
2002-02-21 19:29 ` Alexandre Oliva
2002-02-21 20:41 ` H . J . Lu
2002-02-21 21:02 ` David Edelsohn
2002-02-21 19:05 ` Alexandre Oliva
2002-02-21 16:48 Mark Mitchell
2002-02-21 17:25 ` Joseph S. Myers
2002-02-22 2:06 ` Joseph S. Myers
2002-02-22 12:15 ` Toon Moene
2002-02-24 23:26 ` Mark Mitchell
2002-02-25 20:28 ` David O'Brien
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=40370000.1021615442@gandalf.codesourcery.com \
--to=mark@codesourcery.com \
--cc=aldyh@redhat.com \
--cc=gcc@gcc.gnu.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).