diff options
| author | Aaron Sawdey <acsawdey@linux.ibm.com> | 2020-11-04 13:54:25 -0600 |
|---|---|---|
| committer | Aaron Sawdey <acsawdey@linux.ibm.com> | 2020-11-17 11:10:11 -0500 |
| commit | 6b91b3e9df171970a907638d9b2e0bca1e792975 (patch) | |
| tree | 4520112150212b2ccc3174df9393bad83169aad6 /gcc/dbxout.c | |
| parent | 8661f4faa875f361cd22a197774c1fa04cd0580b (diff) | |
| download | gcc-6b91b3e9df171970a907638d9b2e0bca1e792975.zip gcc-6b91b3e9df171970a907638d9b2e0bca1e792975.tar.gz gcc-6b91b3e9df171970a907638d9b2e0bca1e792975.tar.bz2 | |
Add MODE_OPAQUE
After discussion with Richard Sandiford on IRC, he suggested adding a
new mode class MODE_OPAQUE to deal with the problems (PR 96791) we had
been having with POImode/PXImode in powerpc target. This patch is the
accumulation of changes I needed to make to add this and make it useable
for the purposes of what power10 MMA needed.
MODE_OPAQUE modes allow you to have modes for which you can just
define loads and stores. By design, optimization does not expect to
know how to do arithmetic or subregs on these modes. This allows us to
have modes for multi-register vector operations where we don't want to
open Pandora's Box and define general arithmetic operations.
This patch will be followed by a target specific patch to change the
powerpc power10 MMA builtins to use opaque modes, and will also let use
use the vector pair loads/stores defined with that in the inline expansion
of memcpy/memmove, allowing me to fix PR 96791.
gcc/ChangeLog
PR target/96791
* mode-classes.def: Add MODE_OPAQUE.
* machmode.def: Add OPAQUE_MODE.
* tree.def: Add OPAQUE_TYPE for types that will use
MODE_OPAQUE.
* doc/generic.texi: Document OPAQUE_TYPE.
* doc/rtl.texi: Document MODE_OPAQUE.
* machmode.h: Add OPAQUE_MODE_P().
* genmodes.c (complete_mode): Add MODE_OPAQUE.
(opaque_mode): New function.
* tree.c (tree_code_size): Add OPAQUE_TYPE.
* tree.h: Add OPAQUE_TYPE_P().
* stor-layout.c (int_mode_for_mode): Treat MODE_OPAQUE modes
like BLKmode.
* ira.c (find_moveable_pseudos): Treat MODE_OPAQUE modes more
like integer/float modes here.
* dbxout.c (dbxout_type): Treat OPAQUE_TYPE like VOID_TYPE.
* tree-pretty-print.c (dump_generic_node): Treat OPAQUE_TYPE
like like other types.
Diffstat (limited to 'gcc/dbxout.c')
| -rw-r--r-- | gcc/dbxout.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/gcc/dbxout.c b/gcc/dbxout.c index 5a20fde..eaee2f1 100644 --- a/gcc/dbxout.c +++ b/gcc/dbxout.c @@ -1963,6 +1963,7 @@ dbxout_type (tree type, int full) case VOID_TYPE: case NULLPTR_TYPE: case LANG_TYPE: + case OPAQUE_TYPE: /* For a void type, just define it as itself; i.e., "5=5". This makes us consider it defined without saying what it is. The debugger will make it |