public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Konrad Eisele <konrad@gaisler.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: crossgcc@sourceware.org,
	Ralf Corsepius <ralf.corsepius@rtems.org>,
	       "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Subject: Re: sparc leon  toolchain 4.6.0
Date: Tue, 06 Dec 2011 09:43:00 -0000	[thread overview]
Message-ID: <4EDDE1B5.9040408@gaisler.com> (raw)
In-Reply-To: <201112051227.53498.vapier@gentoo.org>

Mike Frysinger wrote:
> 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

I agree but I keep sending patches
that are not applied. The binutil patch for instance
where sent but ignored. The gcc patch will be ignored too.
It was ebotcazou@adacore.com that decided that sparc-leon[3]
should be the target-vendor standard. I sent the [sf|hf]leon[v8]
variant but it was removed. He has the commit right, so he
decides, I cannot do anything about it. For the time beeing
it might as well be present in crosstools.
-- Konrad


--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2011-12-06  9:43 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
2011-12-06  9:43     ` Konrad Eisele [this message]
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=4EDDE1B5.9040408@gaisler.com \
    --to=konrad@gaisler.com \
    --cc=crossgcc@sourceware.org \
    --cc=ralf.corsepius@rtems.org \
    --cc=vapier@gentoo.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).