From: Alexandre Oliva <aoliva@redhat.com>
To: "Vincent Barat" <vbarat@nexwave-solutions.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: WELCOME to gcc-help@gcc.gnu.org
Date: Fri, 27 Jan 2006 13:43:00 -0000 [thread overview]
Message-ID: <orzmlhzsza.fsf@livre.oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <4573918FB2443A48A55587FF99AD179A2AFB98@millenaire> (Vincent Barat's message of "Fri, 27 Jan 2006 11:08:37 +0100")
On Jan 27, 2006, "Vincent Barat" <vbarat@nexwave-solutions.com> wrote:
> I'm working on a project for which a MN103 compiler is needed. We
> currently use Matsushita's standard compiler, which in turn is gcc 3.2.2
> patched and corrected by RedHat. This one works well, but the
> corrections seem to have never been released to the open source
> community.
I very much doubt it, but if you have any suggestion as to which fixes
failed to make it, please let me know and I'll be happy to have a
look. It's more likely that, if you're playing with newer toolchains
targeted at mn10300-elf or am33_2.0-linux-gnu and they don't quite
work, they're just suffering from bit rot. I know I've neglected
their maintenance for quite a while, but I'm afraid I didn't have much
of a choice.
> Also, I think RedHat should have contributed back to the open source
> community by giving their corrections and patches to the FSF. Am I right
> ?
Yes, and we did that, to the best of my knowledge.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2006-01-27 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 10:08 Vincent Barat
2006-01-27 13:43 ` Alexandre Oliva [this message]
[not found] <1184073227.29349.ezmlm@gcc.gnu.org>
2007-07-10 13:19 ` Arora Yogesh-a22623
[not found] <1095661597.26784.ezmlm@gcc.gnu.org>
2004-09-20 7:37 ` zhiguo ge
[not found] <1062804110.11035.ezmlm@gcc.gnu.org>
2003-09-14 0:39 ` Allen Williams
2003-09-14 13:55 ` Alexandre Oliva
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=orzmlhzsza.fsf@livre.oliva.athome.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=vbarat@nexwave-solutions.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).