public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aaron Sawdey <acsawdey@linux.ibm.com>
To: GCC Development <gcc@gcc.gnu.org>
Subject: Avoiding truncate/sign-extend of POImode on ppc target
Date: Wed, 2 Sep 2020 09:22:18 -0500	[thread overview]
Message-ID: <81D01162-AE8B-4588-847C-0844F405491D@linux.ibm.com> (raw)


PR96791 is happening because DSE is trying to truncate a
POImode reg down to DImode. The POImode is created by a
structure copy that gets inline expanded using lxvp/stxvp
which we have defined using POImode. DSE recognizes that a
following load overlaps with the stxvp and can be satisfied
by a truncation of the POImode reg used for the stxvp.

The intention of using POImode was to avoid having to fully
define OImode and it seems like defining these truncations
would be the first step along that path.  If I haven't
misrepresented it, I believe that is Segher's position on
this.

The function extract_low_bits() in expmed.c does some
querying of the target hook modes_tieable_p but not in any
way that allows us to tell it not to allow truncation of
POImode to a smaller mode.  As a result we run into the ICE
because the patterns are not provided to do this.

So, I put it to the community: Is there an existing way to do
this?  Or, do we need another target hook of some kind to
check this sort of thing?

Thanks,
    Aaron


Aaron Sawdey, Ph.D. sawdey@linux.ibm.com
IBM Linux on POWER Toolchain
 


             reply	other threads:[~2020-09-02 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 14:22 Aaron Sawdey [this message]
2020-09-02 14:27 ` Aaron Sawdey

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=81D01162-AE8B-4588-847C-0844F405491D@linux.ibm.com \
    --to=acsawdey@linux.ibm.com \
    --cc=gcc@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).