aboutsummaryrefslogtreecommitdiff
path: root/contrib/unused_functions.py
diff options
context:
space:
mode:
authorTsukasa OI <research_trasio@irq.a4lg.com>2023-08-11 06:09:34 +0000
committerTsukasa OI <research_trasio@irq.a4lg.com>2023-08-29 13:47:58 +0000
commit8b0662254cdac3e0b670c1c54752e1d43113b0f4 (patch)
treefe9f90adbcd6f353509590b71d85d7ae8c2d1724 /contrib/unused_functions.py
parentb3176bdc86c04da6545a4bd8e2fb7f38d3f2db8d (diff)
downloadgcc-8b0662254cdac3e0b670c1c54752e1d43113b0f4.zip
gcc-8b0662254cdac3e0b670c1c54752e1d43113b0f4.tar.gz
gcc-8b0662254cdac3e0b670c1c54752e1d43113b0f4.tar.bz2
RISC-V: Make PR 102957 tests more comprehensive
Commit c283c4774d1c ("RISC-V: Throw compilation error for unknown extensions") changed how do we handle unknown extensions and commit 6f709f79c915a ("[committed] [RISC-V] Fix expected diagnostic messages in testsuite") "fixed" test failures caused by that change (on pr102957.c, by testing the error message after the first change). However, the latter change will partially break the original intent of PR 102957 test case because we wanted to make sure that we can parse a valid two-letter extension name. Fortunately, there is a valid two-letter extension name, 'Zk' (standard scalar cryptography extension superset with NIST algorithm suite). This commit adds pr102957-2.c to make sure that there will be no errors if we parse a valid two-letter extension name. gcc/testsuite/ChangeLog: * gcc.target/riscv/pr102957-2.c: New test case using the 'Zk' extension to continue testing whether we can use valid two-letter extensions.
Diffstat (limited to 'contrib/unused_functions.py')
0 files changed, 0 insertions, 0 deletions