From: Mike Frysinger <vapier@gentoo.org>
To: crossgcc@sourceware.org
Cc: Ralf Corsepius <ralf.corsepius@rtems.org>,
Konrad Eisele <konrad@gaisler.com>,
"Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Subject: Re: sparc leon toolchain 4.6.0
Date: Mon, 05 Dec 2011 17:28:00 -0000 [thread overview]
Message-ID: <201112051227.53498.vapier@gentoo.org> (raw)
In-Reply-To: <4EDCD1C8.9020608@rtems.org>
[-- Attachment #1: Type: Text/Plain, Size: 339 bytes --]
On Monday 05 December 2011 09:14:32 Ralf Corsepius wrote:
> On 12/05/2011 09:55 AM, Konrad Eisele wrote:
> > Here is a seperated patch for gcc 4.6.0 + binutils 2.21.1 for
> > SPARC-LEON.
>
> These patches belong into upstream gcc and binutils.
>
> Forking gcc/binutils as part of crossgcc isn't helpful.
what Ralf said
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-12-05 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 9:03 Konrad Eisele
2011-12-05 17:16 ` Ralf Corsepius
2011-12-05 17:28 ` Mike Frysinger [this message]
2011-12-06 9:43 ` Konrad Eisele
2011-12-11 21:37 ` Yann E. MORIN
2011-12-12 7:46 ` Konrad Eisele
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=201112051227.53498.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=crossgcc@sourceware.org \
--cc=konrad@gaisler.com \
--cc=ralf.corsepius@rtems.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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).