Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
Time | Test | |
---|---|---|
60,030 ms | x64 debian > libFuzzer.libFuzzer::fuzzer-leak.test | |
60,070 ms | x64 debian > libFuzzer.libFuzzer::large.test |
Event Timeline
Comment Actions
My worry with this is that the top lanes are not always defined to be zero by the DAG nodes. There is a comment in the header that says:
// Vector across-lanes addition // Only the lower result lane is defined.
And they can be selected in a number of ways, things like ADDPv2i64p are defined to produce a scalar results which is inserted into an undef vector.
Maybe that's OK, but we are relying on shaky semantics. Whilst it is true that the ADDV/ADDP instructions clear the top bits (as do many other instruction that set s/d regs), it's not clear to me where that is ensured through the pipeline.
llvm/test/CodeGen/AArch64/vecreduce-zeroing.ll | ||
---|---|---|
6 | We can usually remove dso_local and local_unnamed_addr #0 to clean up the tests a bit. | |
62 | Can these be removed? |
We can usually remove dso_local and local_unnamed_addr #0 to clean up the tests a bit.