public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Roger Sayle <roger@nextmovesoftware.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] i386: Fix up <insn><dwi>3_doubleword_lowpart [PR112523]
Date: Tue, 14 Nov 2023 13:08:44 +0100	[thread overview]
Message-ID: <CAFULd4ZwUbpekYLvz5DcxuQp=GAV_mRm6fi5RJWjHJ-CCkowOQ@mail.gmail.com> (raw)
In-Reply-To: <ZVNi36Ljh1Rhi27B@tucnak>

On Tue, Nov 14, 2023 at 1:07 PM Jakub Jelinek <jakub@redhat.com> wrote:
>
> Hi!
>
> On Sun, Nov 12, 2023 at 09:03:42PM -0000, Roger Sayle wrote:
> > This patch improves register pressure during reload, inspired by PR 97756.
> > Normally, a double-word right-shift by a constant produces a double-word
> > result, the highpart of which is dead when followed by a truncation.
> > The dead code calculating the high part gets cleaned up post-reload, so
> > the issue isn't normally visible, except for the increased register
> > pressure during reload, sometimes leading to odd register assignments.
> > Providing a post-reload splitter, which clobbers a single wordmode
> > result register instead of a doubleword result register, helps (a bit).
>
> Unfortunately this broke bootstrap on i686-linux, broke all ACATS tests
> on x86_64-linux as well as miscompiled e.g. __floattisf in libgcc there
> as well.
>
> The bug is that shrd{l,q} instruction expects the low part of the input
> to be the same register as the output, rather than the high part as the
> patch implemented.
>   split_double_mode (<DWI>mode, &operands[1], 1, &operands[1], &operands[3]);
> sets operands[1] to the lo_half and operands[3] to the hi_half, so if
> operands[0] is not the same register as operands[1] (rather than [3]) after
> RA, we should during splitting move operands[1] into operands[0].
>
> Your testcase:
>
> > #define MASK60 ((1ul << 60) - 1)
> > unsigned long foo (__uint128_t n)
> > {
> >   unsigned long a = n & MASK60;
> >   unsigned long b = (n >> 60);
> >   b = b & MASK60;
> >   unsigned long c = (n >> 120);
> >   return a+b+c;
> > }
>
> still has the same number of instructions.
>
> Bootstrapped/regtested on x86_64-linux (where it e.g. turns
>                 === acats Summary ===
> -# of unexpected failures       2328
> +# of expected passes           2328
> +# of unexpected failures       0
> and fixes gcc.dg/torture/fp-int-convert-*timode.c FAILs as well)
> and i686-linux (where it previously didn't bootstrap, but compared to
> Friday evening's bootstrap the testresults are ok), ok for trunk?
>
> 2023-11-14  Jakub Jelinek  <jakub@redhat.com>
>
>         PR target/112523
>         PR ada/112514
>         * config/i386/i386.md (<insn><dwi>3_doubleword_lowpart): Move
>         operands[1] aka low part of input rather than operands[3] aka high
>         part of input to output if not the same register.

OK.

Thanks,
Uros.

>
> --- gcc/config/i386/i386.md.jj  2023-11-14 08:10:18.932549803 +0100
> +++ gcc/config/i386/i386.md     2023-11-14 09:31:05.565019207 +0100
> @@ -14825,8 +14825,8 @@ (define_insn_and_split "<insn><dwi>3_dou
>  {
>    split_double_mode (<DWI>mode, &operands[1], 1, &operands[1], &operands[3]);
>    operands[4] = GEN_INT ((<MODE_SIZE> * BITS_PER_UNIT) - INTVAL (operands[2]));
> -  if (!rtx_equal_p (operands[0], operands[3]))
> -    emit_move_insn (operands[0], operands[3]);
> +  if (!rtx_equal_p (operands[0], operands[1]))
> +    emit_move_insn (operands[0], operands[1]);
>  })
>
>  (define_insn "x86_64_shrd"
>
>
>         Jakub
>

  reply	other threads:[~2023-11-14 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12 21:03 [x86 PATCH] Improve reg pressure of double-word right-shift then truncate Roger Sayle
2023-11-13  7:23 ` Uros Bizjak
2023-11-14 12:06 ` [PATCH] i386: Fix up <insn><dwi>3_doubleword_lowpart [PR112523] Jakub Jelinek
2023-11-14 12:08   ` Uros Bizjak [this message]
2023-11-14 12:48   ` Richard Biener

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='CAFULd4ZwUbpekYLvz5DcxuQp=GAV_mRm6fi5RJWjHJ-CCkowOQ@mail.gmail.com' \
    --to=ubizjak@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=roger@nextmovesoftware.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).