From: Zack Weinberg <zack@codesourcery.com>
To: Kumar Gala <kumar.gala@motorola.com>
Cc: Aldy Hernandez <aldyh@redhat.com>, <gcc@gcc.gnu.org>
Subject: Re: Branch created: gcc-3_3-e500-branch
Date: Thu, 15 May 2003 04:38:00 -0000 [thread overview]
Message-ID: <87addo25ag.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <26FB3757-868B-11D7-957F-000393DBC2E8@motorola.com> (Kumar Gala's message of "Wed, 14 May 2003 23:10:24 -0500")
Kumar Gala <kumar.gala@motorola.com> writes:
> Zach, Aldy
>
> What's the state of the gcc-3_3-e500-branch?
It works, as far as I know. I need to do another merge from the 3.3
release branch now that GCC 3.3.0 has officially been shipped. I'm
also considering applying David Edelsohn's patches for the 440 chip;
it's not strictly relevant to the e500, but my clients want it.
> Is it feasible to merge it back into 3.3 so that 3.3.1 has fully
> working e500 support?
That's a question you should be asking the PowerPC port maintainers
and the release manager, not either of us. I would like to see it
happen; however, some of the changes I had to backport could be seen
as risky, such as the 3.4 genautomata.c (although not any of the rest
of the scheduler).
zw
next prev parent reply other threads:[~2003-05-15 4:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 22:07 Zack Weinberg
2003-04-16 1:15 ` Kumar Gala
2003-04-16 1:16 ` Zack Weinberg
2003-04-16 9:25 ` Kumar Gala
2003-04-16 16:09 ` Aldy Hernandez
2003-04-16 16:15 ` Kumar Gala
2003-04-16 16:50 ` Aldy Hernandez
2003-04-16 22:19 ` Jan Hubicka
2003-04-17 4:54 ` Zack Weinberg
2003-04-17 16:46 ` Aldy Hernandez
2003-04-17 17:28 ` Zack Weinberg
2003-05-15 4:10 ` Kumar Gala
2003-05-15 4:38 ` Zack Weinberg [this message]
2003-05-15 14:41 ` Kumar Gala
2003-05-15 15:43 ` Mark Mitchell
2003-05-15 20:14 ` Geoff Keating
2003-05-15 14:45 ` altivec testsuite Kumar Gala
2003-04-16 14:14 ` Branch created: gcc-3_3-e500-branch Gerald Pfeifer
2003-04-16 17:16 ` Zack Weinberg
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=87addo25ag.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=kumar.gala@motorola.com \
/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).