- There is no tests for mabi=ilp32e, and my patch covers that.
- The tests in riscv-abi.c will show default ABI changes for special archs in the future, especially the arch with the F but without the D extension.
- The tests in riscv-arch.c will show default arch changes for abi=ilp32, which is rv32imacfd currently, but it is better to be rv32imac. And it is also better for abi=ilp32f defaults to arch=imacf.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
How to formulate the default abi and arch is still under discussion.
https://github.com/riscv/riscv-toolchain-conventions/issues/13
But the tests can be added first, for contrast of future changes.
Comment Actions
How do the new tests provide additional coverage?
clang/test/Driver/riscv-arch.c | ||
---|---|---|
45 | I suggest the style used in linux-cross.cpp Just using -SAME cannot detect unrelated strings between "-target-feature" "+m" and "-target-feature" "+f" |
clang/test/Driver/riscv-arch.c | ||
---|---|---|
45 | Thanks for your suggestion. |
Comment Actions
For these tests,
- there is no tests for mabi=ilp32e, and my patch covers that.
- the tests in riscv-abi.c will show default abi changes for special archs, especially for the arch with F but without D extension, in the future.
- the tests in riscv-arch.c will show default arch changes for abi=ilp32, which is rv32imacfd now, and it is better to be rv32imac. for abi=ilp32f it is better arch=imacf than current imacfd.
Comment Actions
LGTM.
clang/test/Driver/riscv-arch.c | ||
---|---|---|
122 | // CHECK-LP64F: "-target-feature" "+m" // CHECK-LP64F-SAME: {{^}} "-target-feature" "+a" |
I suggest the style used in linux-cross.cpp
Just using -SAME cannot detect unrelated strings between "-target-feature" "+m" and "-target-feature" "+f"