From: Evgeny Stupachenko <evstupac@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Uros Bizjak <ubizjak@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 14:09:00 -0000 [thread overview]
Message-ID: <CAOvf_xxiBjV0uykgC7BFL1tyan9pEDUqkvYOtA=8EgVxki=fEg@mail.gmail.com> (raw)
In-Reply-To: <20141010123650.GK10376@tucnak.redhat.com>
Updated ChangeLog:
2014-10-10 Ilya Enkovich <ilya.enkovich@intel.com>
Vladimir Makarov <vmakarov@redhat.com>
* config/i386/i386.c (ix86_use_pseudo_pic_reg): New.
(ix86_init_pic_reg): New.
(ix86_select_alt_pic_regnum): Add check on pseudo register.
(ix86_save_reg): Likewise.
(ix86_expand_prologue): Remove PIC register initialization
now performed in ix86_init_pic_reg.
(ix86_output_function_epilogue): Add check on pseudo register.
(set_pic_reg_ever_alive): New.
(legitimize_pic_address): Replace df_set_regs_ever_live with new
set_pic_reg_ever_alive.
(legitimize_tls_address): Likewise.
(ix86_pic_register_p): New check.
(ix86_delegitimize_address): Add check on pseudo register.
(ix86_expand_call): Insert move from pseudo PIC register to ABI
defined REAL_PIC_OFFSET_TABLE_REGNUM.
(TARGET_INIT_PIC_REG): New.
(TARGET_USE_PSEUDO_PIC_REG): New.
* config/i386/i386.h (PIC_OFFSET_TABLE_REGNUM): Return INVALID_REGNUM
if pic_offset_table_rtx exists.
>- if (pic_offset_table_rtx)
>+ if (pic_offset_table_rtx
>+ && (!reload_completed || !ix86_use_pseudo_pic_reg ()))
>Hm, can you please add a comment for this change?
I've added the following comment to the patch:
- in which case we return (%ecx - %ebx) + foo. */
+ in which case we return (%ecx - %ebx) + foo.
+
+ Note that when pseudo_pic_reg is used we can generate it only
+ before reload_completed. */
On Fri, Oct 10, 2014 at 4:36 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Fri, Oct 10, 2014 at 02:34:07PM +0200, Rainer Orth wrote:
>> 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.
>
> And add a blank line after after the e-mail lines.
>
> Jakub
next prev parent reply other threads:[~2014-10-10 14:01 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
2014-10-10 12:38 ` Jakub Jelinek
2014-10-10 14:09 ` Evgeny Stupachenko [this message]
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='CAOvf_xxiBjV0uykgC7BFL1tyan9pEDUqkvYOtA=8EgVxki=fEg@mail.gmail.com' \
--to=evstupac@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=law@redhat.com \
--cc=ro@cebitec.uni-bielefeld.de \
--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).