From: Uros Bizjak <ubizjak@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix ix86_split_long_move collision handling with TLS (PR target/66470)
Date: Tue, 09 Jun 2015 19:17:00 -0000 [thread overview]
Message-ID: <CAFULd4ag80XLNrt0SP=fB8B=ywM=A2k6rP31=VSzz+x7b4mBAQ@mail.gmail.com> (raw)
In-Reply-To: <20150609162132.GE10247@tucnak.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
On Tue, Jun 9, 2015 at 6:21 PM, Jakub Jelinek <jakub@redhat.com> wrote:
> On Tue, Jun 09, 2015 at 06:16:32PM +0200, Uros Bizjak wrote:
>> > something? Would it be acceptable to just guard the changes in the patch
>> > with !TARGET_X32 and let H.J. deal with that target? I'm afraid I'm lost
>> > when to ZERO_EXTEND addr (if needed at all), etc.
>>
>> If you wish, I can take your patch and take if further. -mx32 is a
>> delicate beast...
>
> If you could, it would be appreciated, I'm quite busy with OpenMP 4.1 stuff
> now.
> Note that for -m64/-mx32 it will be much harder to create a reproducer,
> because to trigger the bug one has to convince the register allocator
> to allocate the lhs of the load in certain registers (not that hard),
> but also the index register (to be scaled, also not that hard) and
> also the register holding the tls symbol immediate. Wonder if one has to
> keep all but the two registers live across the load or something similar.
Please find attach a patch that takes your idea slightly further. We
find perhaps zero-extended UNSPEC_TP, and copy it for further use. At
its place, we simply slap const0_rtx. We know that address to
multi-word values has to be offsettable, which in case of x32 means
that it is NOT zero-extended address.
Uros.
[-- Attachment #2: r.diff.txt --]
[-- Type: text/plain, Size: 2063 bytes --]
Index: config/i386/i386.c
===================================================================
--- config/i386/i386.c (revision 224292)
+++ config/i386/i386.c (working copy)
@@ -22858,7 +22858,7 @@ ix86_split_long_move (rtx operands[])
Do an lea to the last part and use only one colliding move. */
else if (collisions > 1)
{
- rtx base;
+ rtx base, addr, tls_base = NULL_RTX;
collisions = 1;
@@ -22869,10 +22869,52 @@ ix86_split_long_move (rtx operands[])
if (GET_MODE (base) != Pmode)
base = gen_rtx_REG (Pmode, REGNO (base));
- emit_insn (gen_rtx_SET (base, XEXP (part[1][0], 0)));
+ addr = XEXP (part[1][0], 0);
+ if (TARGET_TLS_DIRECT_SEG_REFS)
+ {
+ struct ix86_address parts;
+ int ok = ix86_decompose_address (addr, &parts);
+ gcc_assert (ok);
+ if (parts.seg != SEG_DEFAULT)
+ {
+ /* It is not valid to use %gs: or %fs: in
+ lea though, so we need to remove it from the
+ address used for lea and add it to each individual
+ memory loads instead. */
+ rtx *x = &addr;
+ while (GET_CODE (*x) == PLUS)
+ {
+ for (i = 0; i < 2; i++)
+ {
+ rtx op = XEXP (*x, i);
+ if ((GET_CODE (op) == UNSPEC
+ && XINT (op, 1) == UNSPEC_TP)
+ || (GET_CODE (op) == ZERO_EXTEND
+ && GET_CODE (XEXP (op, 0)) == UNSPEC
+ && (XINT (XEXP (op, 0), 1)
+ == UNSPEC_TP)))
+ {
+ tls_base = XEXP (*x, i);
+ XEXP (*x, i) = const0_rtx;
+ break;
+ }
+ }
+
+ if (tls_base)
+ break;
+ x = &XEXP (*x, 0);
+ }
+ gcc_assert (tls_base);
+ }
+ }
+ emit_insn (gen_rtx_SET (base, addr));
+ if (tls_base)
+ base = gen_rtx_PLUS (GET_MODE (base), base, tls_base);
part[1][0] = replace_equiv_address (part[1][0], base);
for (i = 1; i < nparts; i++)
{
+ if (tls_base)
+ base = copy_rtx (base);
tmp = plus_constant (Pmode, base, UNITS_PER_WORD * i);
part[1][i] = replace_equiv_address (part[1][i], tmp);
}
next prev parent reply other threads:[~2015-06-09 18:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 12:05 Jakub Jelinek
2015-06-09 12:32 ` Uros Bizjak
2015-06-09 12:57 ` Jakub Jelinek
2015-06-09 13:26 ` Uros Bizjak
2015-06-09 13:44 ` Jakub Jelinek
2015-06-09 14:06 ` Uros Bizjak
2015-06-09 14:21 ` Uros Bizjak
2015-06-09 14:44 ` Jakub Jelinek
2015-06-09 16:19 ` Uros Bizjak
2015-06-09 16:57 ` Jakub Jelinek
2015-06-09 19:17 ` Uros Bizjak [this message]
2015-06-09 20:11 ` Jakub Jelinek
2015-06-10 6:38 ` Uros Bizjak
2015-06-10 6:43 ` Richard Sandiford
2015-06-10 7:07 ` Jakub Jelinek
2015-06-10 7:13 ` Uros Bizjak
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='CAFULd4ag80XLNrt0SP=fB8B=ywM=A2k6rP31=VSzz+x7b4mBAQ@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@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).