Hi Robin,
Yes, you're right, this should not be necessary. This is more of a
test for the execution environment than the compiler. I think Juzhe
removed it already in his patch that enables the vector test suite.
In the future we would use the checks that Joern added, not sure if
they are alre
Hi Lehua,
> May I ask if the compiler options "-march=rv64gcv_zvfh -mabi=lp64d"
> should be removed? Because we don't specify -march and -mabi when we
> run testcase (so but why we need to specify the -march and -mabi in
> this target check?), we run it with the default values. Assuming that
> t
Hi Robin,
+# Return 1 if the we can build a vector example with proper -march flags
+# and the current target can execute it, 0 otherwise. Cache the result.
+
+proc check_effective_target_riscv_vector_hw { } {
+
+return [check_runtime riscv_vector_hw32 {
+int main (void)
+{
On 6/16/23 07:43, juzhe.zhong wrote:
lgtm
ACK for the trunk.
jeff
Hi,
changes in v3:
- No longer "dependent" on testsuite changes. Just the zvfh
run testcases use riscv_zvfh_hw, i.e. require that we can compile,
link the code as well as execute the resulting binary.
- Renamed rounding modes (floating_point_rounding_mode feels a
bit long-winded but well...)
