Hi Kazu,
> fr30
>
>
> The same justification as
>
>http://gcc.gnu.org/ml/gcc/2004-06/msg01113.html
>
> Nobody showed an interest in keeping this port.
I would like to keep this port alive. I happen to know that Fujitsu
are still involved with developing and marketing it and that the
Kazu Hirata wrote:
ip2k
This is an Ubicom cpu, and they maintain a GNU port in house. There are
references to it on their web site, though I didn't see a convenient
link to download it. Probably not much worth to the FSF version of this
port if they aren't contributing patches to it.
ns32k
Ev
On Tue, 22 Mar 2005, Kazu Hirata wrote:
> > We would like to merge our changes with mainline, 4.0 branch
> > and the 3.4 branch and continue work in the FSF domain. What
> > would be the best way to go about this ?
>
> Send patches to [EMAIL PROTECTED] If you are familiar with ARC
> and willin
Hi Ramana,
> PR8972 has been fixed in our tree and we should be pushing
> the patch upstream soon. We had got the FSF tree building
> with patches to fix PR17317 / PR11476 / PR17240 .We have
> also been making fixes with binutils which can be found in
> the corresponding archives.
If that's
Hi,
Resending for the archives, since the spam bot on sourceware
did not like so many recipients with my address. Hope it
works this time and apologies for duplicate messages .
cheers
Ramana
Original Message
Subject: Re: Obsoleting more ports for 4.0.
Date: Tue, 22 Mar 2005 18
Kazu Hirata wrote:
Hi,
First off, Mark, if you think this stuff is too late for 4.0, I'll
postpone this to 4.1. Please note that all we have to do is add a few
lines to config.gcc as far as printing the "obsolete" message is
concerned.
I think that if you get no objections to your message within a
Hi,
First off, Mark, if you think this stuff is too late for 4.0, I'll
postpone this to 4.1. Please note that all we have to do is add a few
lines to config.gcc as far as printing the "obsolete" message is
concerned.
Below, I propose to obsolete the following three architectures for GCC
4.0 and
