From: Uros Bizjak <ubizjak@gmail.com>
To: Hongtao Liu <crazylht@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH]Don't use pinsr for struct initialization.
Date: Tue, 18 Aug 2020 08:09:22 +0200 [thread overview]
Message-ID: <CAFULd4abP44Ji-=XwvszXzNQoyu7heqtMJy+5Gus0rrrLakixw@mail.gmail.com> (raw)
In-Reply-To: <CAMZc-bzdFfOp1nLCY3cH78WZr1DXdvqMqg6bVycw__FPioRBHA@mail.gmail.com>
On Tue, Aug 18, 2020 at 4:23 AM Hongtao Liu <crazylht@gmail.com> wrote:
>
> On Fri, Aug 14, 2020 at 5:57 PM Uros Bizjak <ubizjak@gmail.com> wrote:
> >
> > On Fri, Aug 14, 2020 at 8:03 AM Hongtao Liu <crazylht@gmail.com> wrote:
> > >
> > > Hi:
> > > For struct initialization, when it fits in a TImode, gcc will use
> > > pinsr insn which causes poor codegen described in PR93897 and PR96562.
> >
> > You should probably remove TImode handling also from ix86_expand_pextr.
> >
>
> Yes, but i failed to construct a testcase to cover this part.
> Anyway, the regression test for i386/x86-64 backend is ok, bootstrap is ok.
> I also run the patch on SPEC2017, no big impact.
>
> > Uros.
> >
> > > Bootstrap is ok, regression test is ok for i386/x86-64 backend.
> > > Ok for trunk?
> > >
> > > ChangeLog
> > > gcc/
> > > PR target/96562
> > > PR target/93897
> > > * config/i386/i386-expand.c (ix86_expand_pinsr): Don't use
> > > pinsr for TImode.
> > >
> > > gcc/testsuite/
> > > * gcc.target/i386/pr96562-1.c: New test.
> > >
> > > --
> > > BR,
> > > Hongtao
>
> Update patch.
OK for mainline and backports.
Thanks,
Uros.
prev parent reply other threads:[~2020-08-18 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 6:03 Hongtao Liu
2020-08-14 9:57 ` Uros Bizjak
2020-08-18 2:24 ` Hongtao Liu
2020-08-18 6:09 ` Uros Bizjak [this message]
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='CAFULd4abP44Ji-=XwvszXzNQoyu7heqtMJy+5Gus0rrrLakixw@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/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).