public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Kirill Yukhin <kirill.yukhin@gmail.com>
Cc: Maxim Kuvyrkov <maxim@kugelworks.com>,
	       Alexander Ivchenko <aivchenk@gmail.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC PATCH] Implementing ifunc target hook
Date: Tue, 02 Apr 2013 13:49:00 -0000	[thread overview]
Message-ID: <20130402132434.GN20616@tucnak.redhat.com> (raw)
In-Reply-To: <CAGs3Rftmx0GmFh6LE3C70G5DfAk5Vu6aEjsJF-8L0zZJe3kkJw@mail.gmail.com>

On Wed, Mar 27, 2013 at 01:56:48PM +0400, Kirill Yukhin wrote:
> >
> > Otherwise OK.
> >
> > Thanks,
> 
> Hi,  chacked into trunk: http://gcc.gnu.org/ml/gcc-cvs/2013-03/msg00785.html

This leads to:
../../gcc/config/t-linux-android:22: warning: overriding recipe for target `linux-android.o'
../../gcc/config/t-linux-android:22: warning: ignoring old recipe for target `linux-android.o'
for arm*-linux* target (cross in my case).  t-linux-android is listed twice.

	Jakub

  reply	other threads:[~2013-04-02 13:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26 12:15 Alexander Ivchenko
2012-12-26 17:06 ` Joseph S. Myers
2012-12-27 22:59 ` Maxim Kuvyrkov
2012-12-28 12:30   ` Alexander Ivchenko
2013-01-02 23:08     ` Maxim Kuvyrkov
2013-01-09 11:24       ` Alexander Ivchenko
2013-01-10 23:24         ` Maxim Kuvyrkov
2013-01-14 15:55           ` Alexander Ivchenko
2013-01-15  4:13             ` Maxim Kuvyrkov
2013-03-26 15:15               ` Alexander Ivchenko
2013-03-26 20:59                 ` Maxim Kuvyrkov
2013-03-27  9:56                   ` Kirill Yukhin
2013-04-02 13:49                     ` Jakub Jelinek [this message]
2013-04-02 14:54                       ` Alexander Ivchenko
2013-04-02 15:04                         ` Jakub Jelinek
2013-04-02 15:06                           ` Kirill Yukhin

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=20130402132434.GN20616@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=aivchenk@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kirill.yukhin@gmail.com \
    --cc=maxim@kugelworks.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).