From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Evgeny Stupachenko <evstupac@gmail.com>,
Jeff Law <law@redhat.com>,
Vladimir Makarov <vmakarov@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 2/X, i386, PR54232] Enable EBX for x86 in 32bits PIC code
Date: Fri, 10 Oct 2014 12:37:00 -0000 [thread overview]
Message-ID: <ydda95414u8.fsf@lokon.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <CAFULd4ZdrAfLVD58kOPaFPdXG_ry8p_w0ho+SqHk3Sotcy9TwQ@mail.gmail.com> (Uros Bizjak's message of "Fri, 10 Oct 2014 14:27:00 +0200")
Uros Bizjak <ubizjak@gmail.com> writes:
> On Fri, Oct 10, 2014 at 9:43 AM, Evgeny Stupachenko <evstupac@gmail.com> wrote:
>> i386 specific part of the patch:
>>
>> 2014-10-08 Ilya Enkovich <ilya.enkovich@intel.com>
>> Vladimir Makarov <vmakarov@redhat.com>
>> * gcc/config/i386/i386.c (ix86_use_pseudo_pic_reg): New.
Evgeny: here and in your other submissions: drop the gcc prefix from the
pathnames. They are all relative to the directory the ChangeLog lives
in.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2014-10-10 12:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 7:54 Evgeny Stupachenko
2014-10-10 10:41 ` Uros Bizjak
2014-10-10 12:34 ` Uros Bizjak
2014-10-10 12:37 ` Rainer Orth [this message]
2014-10-10 12:38 ` Jakub Jelinek
2014-10-10 14:09 ` Evgeny Stupachenko
2014-10-13 15:03 ` Evgeny Stupachenko
2014-10-13 16:10 ` Uros Bizjak
2014-10-24 23:21 ` Andrew Pinski
2014-10-24 23:38 ` Evgeny Stupachenko
2014-10-24 23:48 ` Jeff Law
2014-10-30 8:52 ` Zamyatin, Igor
2014-10-30 9:13 ` Jakub Jelinek
2014-10-30 13:09 ` Zamyatin, Igor
2014-10-30 13:19 ` Jakub Jelinek
2014-10-31 10:06 ` Zamyatin, Igor
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=ydda95414u8.fsf@lokon.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=evstupac@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=ubizjak@gmail.com \
--cc=vmakarov@redhat.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).