From: Uros Bizjak <ubizjak@gmail.com>
To: Ilya Enkovich <enkovich.gnu@gmail.com>
Cc: gcc@gnu.org, "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Evgeny Stupachenko <evstupac@gmail.com>,
Richard Biener <richard.guenther@gmail.com>,
Jeff Law <law@redhat.com>,
Vladimir Makarov <vmakarov@redhat.com>
Subject: Re: Enable EBX for x86 in 32bits PIC code
Date: Thu, 28 Aug 2014 18:58:00 -0000 [thread overview]
Message-ID: <CAFULd4Y-WJqUGMs_wWgFAOy-3e6KPs1ConPCB00muwZfDAU=-w@mail.gmail.com> (raw)
In-Reply-To: <20140822121151.GA60032@msticlxl57.ims.intel.com>
On Fri, Aug 22, 2014 at 2:21 PM, Ilya Enkovich <enkovich.gnu@gmail.com> wrote:
> On Cauldron 2014 we had a couple of talks about relaxation of ebx usage in 32bit PIC mode. It was decided that the best approach would be to not fix ebx register, use speudo register for GOT base address and let allocator do the rest. This should be similar to how clang and icc work with GOT base address. I've been working for some time on such patch and now want to share my results.
> (define_insn "*pushtf"
> [(set (match_operand:TF 0 "push_operand" "=<,<")
> - (match_operand:TF 1 "general_no_elim_operand" "x,*roF"))]
> + (match_operand:TF 1 "nonimmediate_no_elim_operand" "x,*roF"))]
Can you please explain the reason for this change (and a couple of
similar changes to push patterns) ?
Uros.
next prev parent reply other threads:[~2014-08-28 18:58 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOvf_xxsQ_oYGqNAVQ1+BW+CuD3mzebZ2xma0jpF=WfyZMCRCA@mail.gmail.com>
[not found] ` <CAFiYyc1mFtTezkTJORmJJq+yht=qPSwiN7KDn19+bSuSdaqvMQ@mail.gmail.com>
[not found] ` <CAOvf_xyeVeg2oB9Xxz8RMEQ6gyfJY5whd9s4ygoAAEaMU9efnA@mail.gmail.com>
[not found] ` <20140707114750.GB31640@tucnak.redhat.com>
[not found] ` <CAMbmDYZV_fx0jxmKHhLsC2pJ7pDzuu6toEAH72izOdpq6KGyfg@mail.gmail.com>
2014-08-22 12:21 ` Ilya Enkovich
2014-08-23 1:47 ` Hans-Peter Nilsson
2014-08-25 9:25 ` Ilya Enkovich
2014-08-25 11:24 ` Hans-Peter Nilsson
2014-08-25 11:43 ` Ilya Enkovich
2014-08-25 15:09 ` Vladimir Makarov
2014-08-26 7:49 ` Ilya Enkovich
2014-08-26 8:57 ` Ilya Enkovich
2014-08-26 15:25 ` Vladimir Makarov
2014-08-26 21:42 ` Ilya Enkovich
2014-08-27 20:19 ` Vladimir Makarov
2014-08-28 8:28 ` Ilya Enkovich
2014-08-29 6:47 ` Ilya Enkovich
2014-09-02 14:29 ` Vladimir Makarov
2014-09-03 20:19 ` Vladimir Makarov
[not found] ` <0EFAB2BDD0F67E4FB6CCC8B9F87D756969B3A89D@IRSMSX101.ger.corp.intel.com>
2014-09-09 16:43 ` Vladimir Makarov
2014-09-11 19:57 ` Jeff Law
2014-09-23 13:54 ` Ilya Enkovich
2014-09-23 14:23 ` Uros Bizjak
2014-09-23 15:59 ` Jeff Law
2014-09-23 14:34 ` Jakub Jelinek
2014-09-23 15:59 ` Petr Machata
2014-09-23 16:00 ` Jeff Law
2014-09-23 16:03 ` Jakub Jelinek
2014-09-23 16:10 ` Jeff Law
2014-09-24 6:56 ` Ilya Enkovich
2014-09-24 15:27 ` Jeff Law
2014-09-24 20:32 ` Ilya Enkovich
2014-09-24 21:20 ` Jeff Law
2014-09-29 11:09 ` Jakub Jelinek
2014-10-21 16:05 ` [PATCH] Improve i?86 address delegitimization after 32-bit pic changes (PR target/63542) Jakub Jelinek
2014-10-22 2:02 ` Jeff Law
2014-11-24 15:57 ` H.J. Lu
2014-08-27 21:39 ` Enable EBX for x86 in 32bits PIC code Jeff Law
2014-08-28 8:37 ` Ilya Enkovich
2014-08-28 12:43 ` Uros Bizjak
2014-08-28 12:54 ` Ilya Enkovich
2014-08-28 13:08 ` Uros Bizjak
2014-08-28 13:29 ` Ilya Enkovich
2014-08-28 16:25 ` Uros Bizjak
2014-08-29 18:56 ` Jeff Law
2014-08-25 17:30 ` Jeff Law
2014-08-28 13:01 ` Uros Bizjak
2014-08-28 13:13 ` Ilya Enkovich
2014-08-28 18:30 ` Florian Weimer
2014-08-29 18:48 ` Jeff Law
2014-08-28 18:58 ` Uros Bizjak [this message]
2014-08-29 6:51 ` Ilya Enkovich
2014-08-29 18:45 ` Jeff Law
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='CAFULd4Y-WJqUGMs_wWgFAOy-3e6KPs1ConPCB00muwZfDAU=-w@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=enkovich.gnu@gmail.com \
--cc=evstupac@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gnu.org \
--cc=law@redhat.com \
--cc=richard.guenther@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).