aboutsummaryrefslogtreecommitdiff
path: root/gcc/tree-pass.h
diff options
context:
space:
mode:
authorTsukasa OI <research_trasio@irq.a4lg.com>2023-09-03 12:39:47 +0000
committerTsukasa OI <research_trasio@irq.a4lg.com>2023-09-06 02:00:13 +0000
commitce65641354d98fc80912d5516b7fea87c344c2cc (patch)
tree010c76ef84279845f444861261f25a062f96b4e9 /gcc/tree-pass.h
parent4388bc8213a713047fbaac2ca438c8233cde03f5 (diff)
downloadgcc-ce65641354d98fc80912d5516b7fea87c344c2cc.zip
gcc-ce65641354d98fc80912d5516b7fea87c344c2cc.tar.gz
gcc-ce65641354d98fc80912d5516b7fea87c344c2cc.tar.bz2
RISC-V: Fix Zicond ICE on large constants
Large constant cons and/or alt will trigger ICEs building GCC target libraries (libgomp and libatomic) when the 'Zicond' extension is enabled. For instance, zicond-ice-2.c (new test case in this commit) will cause an ICE when SOME_NUMBER is 0x1000 or larger. While opposite numbers corresponding cons/alt (two temp2 variables) are checked, cons/alt themselves are not checked and causing 2 ICEs building GCC target libraries as of this writing: 1. gcc/libatomic/config/posix/lock.c 2. gcc/libgomp/fortran.c Coercing a large value into a register will fix the issue. It also coerce a large cons into a register on "imm, imm" case (the author could not reproduce but possible to cause an ICE). gcc/ChangeLog: * config/riscv/riscv.cc (riscv_expand_conditional_move): Force large constant cons/alt into a register. gcc/testsuite/ChangeLog: * gcc.target/riscv/zicond-ice-2.c: New test. This is based on an ICE at libat_lock_n func on gcc/libatomic/config/posix/lock.c but heavily minimized.
Diffstat (limited to 'gcc/tree-pass.h')
0 files changed, 0 insertions, 0 deletions