public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Raymes Khoury <raymes.khoury@gmail.com>
Cc: hjl.tools@gmail.com, gcc-patches@gcc.gnu.org
Subject: Re: RFA/RFC: Enable both gold and ld in a single toolchain
Date: Tue, 17 Aug 2010 09:27:00 -0000	[thread overview]
Message-ID: <4C6A4F53.2050208@redhat.com> (raw)
In-Reply-To: <AANLkTikmXiDVJ9LF2kZ6ciBVg5_eXa5VkVt6LDgWgGPO@mail.gmail.com>

Hi Raymes,

> What is the status of this patch? I see the binutils part applied but
> not the gcc part.
>
> http://gcc.gnu.org/ml/gcc-patches/2010-04/msg00402.html

Mark Mitchell recently posted a review of the patch and it is currently 
in my queue of things to look at.  Unfortunately I have a few other, 
higher priority tasks on my plate at the moment.  But I will get back to 
the patch as soon as I can.

Cheers
   Nick

  reply	other threads:[~2010-08-17  8:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTiktR5Baeiy6hyHKZy0qLiGDyDEd+m2km+5Me1P0@mail.gmail.com>
2010-08-12 18:19 ` Raymes Khoury
2010-08-17  9:27   ` Nick Clifton [this message]
2011-03-08 19:53     ` Diego Novillo
2011-03-15 11:52       ` Nick Clifton
2011-03-15 18:22       ` Matthias Klose
2010-03-04 19:26 Nick Clifton
2010-03-04 20:47 ` H.J. Lu
2010-03-09 10:09   ` Nick Clifton
2010-03-09 13:54     ` Matthias Klose
2010-03-11  7:41       ` Ryan Hill
2010-03-11 14:53         ` Nick Clifton
2010-03-11 15:07           ` H.J. Lu
2010-03-16 17:34             ` Nick Clifton
2010-03-16 17:49               ` H.J. Lu
2010-03-16 17:56                 ` Nick Clifton
2010-03-16 17:59                   ` H.J. Lu
2010-03-17  8:55                     ` Nick Clifton
2010-03-17 13:54                       ` H.J. Lu
2010-03-16 18:40                   ` Vladimir Simonov
2010-03-17  8:37                     ` Nick Clifton
2010-03-17  8:58                       ` Steven Bosscher
2010-03-17 13:24                       ` Vladimir Simonov
2010-03-18  3:13                     ` Ian Lance Taylor
2010-03-17 16:27               ` H.J. Lu
2010-03-21 15:09               ` Matthias Klose
2010-03-22  1:14               ` Matthias Klose
2010-03-31 15:31               ` Daniel Jacobowitz
2010-03-31 15:51                 ` H.J. Lu
2010-04-09  8:46                   ` Nick Clifton
2010-04-09 16:31                     ` Matthias Klose
2010-04-09 16:37                     ` H.J. Lu
2010-04-09 16:48                       ` H.J. Lu
2010-04-09 17:45                         ` H.J. Lu
2010-04-09 18:52                           ` Ralf Wildenhues
2010-04-09 21:10                             ` H.J. Lu
2010-04-10  4:07                               ` H.J. Lu
2010-04-19 18:17                                 ` H.J. Lu
2010-04-27 14:36                                   ` Nick Clifton
2010-04-27 17:50                                     ` H.J. Lu
2010-03-09 14:10     ` H.J. Lu
2010-03-09 15:08       ` Richard Guenther
2010-03-05  1:05 ` Ralf Wildenhues
     [not found] ` <20100304205859.GE22496__42407.8206219294$1267753343$gmane$org@gmx.de>
2010-03-05 10:06   ` Andreas Schwab
2010-03-09 17:13 ` Paolo Bonzini

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=4C6A4F53.2050208@redhat.com \
    --to=nickc@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=raymes.khoury@gmail.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).