diff options
| author | Jiufu Guo <guojiufu@linux.ibm.com> | 2023-06-09 16:30:54 +0800 |
|---|---|---|
| committer | Jiufu Guo <guojiufu@linux.ibm.com> | 2023-06-19 10:44:39 +0800 |
| commit | c0bd79300e8fad52ec0fac7c65838a525d544a25 (patch) | |
| tree | 02d1128af4b2edae5e1a2e2f4304752875002222 /gcc/tree-vectorizer.h | |
| parent | f8e02702726d4514b8ff9f5481c9c1f5d34e1787 (diff) | |
| download | gcc-c0bd79300e8fad52ec0fac7c65838a525d544a25.zip gcc-c0bd79300e8fad52ec0fac7c65838a525d544a25.tar.gz gcc-c0bd79300e8fad52ec0fac7c65838a525d544a25.tar.bz2 | |
Check SCALAR_INT_MODE_P in try_const_anchors
The const_anchor in cse.cc supports integer constants only.
There is a "gcc_assert (SCALAR_INT_MODE_P (mode))" in
try_const_anchors.
In the latest code, some non-integer modes are used with const int.
For examples:
"set (mem/c:BLK (xx) (const_int 0 [0])" occur in md files of
rs6000, i386, arm, and pa. For this, the mode may be BLKmode.
Pattern "(set (strict_low_part (xx)) (const_int xx))" could
be generated in a few ports. For this, the mode may be VOIDmode.
So, avoid mode other than SCALAR_INT_MODE in try_const_anchors
would be needed.
Some discussions in the previous thread:
https://gcc.gnu.org/pipermail/gcc-patches/2023-June/621097.html
gcc/ChangeLog:
* cse.cc (try_const_anchors): Check SCALAR_INT_MODE.
Diffstat (limited to 'gcc/tree-vectorizer.h')
0 files changed, 0 insertions, 0 deletions