aboutsummaryrefslogtreecommitdiff
path: root/libgcc
diff options
context:
space:
mode:
authorJin Ma <jinma@linux.alibaba.com>2023-11-09 15:40:08 +0800
committerKito Cheng <kito.cheng@sifive.com>2023-11-09 15:59:39 +0800
commit5e9fb75840e10bff5850ee610ca94c889c9a78e5 (patch)
tree37d89a5289b52e3010f4488fc8231d1b6e907b5c /libgcc
parentf586515accd0bafffba88ab906c6c43534a2ad94 (diff)
downloadgcc-5e9fb75840e10bff5850ee610ca94c889c9a78e5.zip
gcc-5e9fb75840e10bff5850ee610ca94c889c9a78e5.tar.gz
gcc-5e9fb75840e10bff5850ee610ca94c889c9a78e5.tar.bz2
RISC-V: Fix the illegal operands for the XTheadMemidx extension.
The pattern "*extend<SHORT:mode><SUPERQI:mode>2_bitmanip" and "*zero_extendhi<GPR:mode>2_bitmanip" in bitmanip.md are similar to the pattern "*th_memidx_bb_extendqi<SUPERQI:mode>2" and "*th_memidx_bb_zero_extendhi<GPR:mode>2" in thead.md, which will cause the wrong instruction to be generated and report the following error in binutils: Assembler messages: Error: illegal operands `lb a5,(a0),1,0' In fact, the correct instruction is "th.lbia a5,(a0),1,0". gcc/ChangeLog: * config/riscv/bitmanip.md: Avoid the conflict between zbb and xtheadmemidx in patterns. gcc/testsuite/ChangeLog: * gcc.target/riscv/xtheadfmemidx-uindex-zbb.c: New test.
Diffstat (limited to 'libgcc')
0 files changed, 0 insertions, 0 deletions