Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Some logic seems to be duplicated here as well. It is called from:
Note sure if we want to keep them.
In general I think this makes a lot more sense.
At first I though that targets that previously did not use bzero (e.g. Arm, SystemZ) would start emitting it. However I had a look at the availability of bzero: it looks like only darwin x86 on MacOSX>10.6 and darwin aarch64 have it, so this looks like a noop.
llvm/test/CodeGen/AArch64/arm64_32.ll | ||
---|---|---|
754 | Why is this not a noop ? |
llvm/test/CodeGen/AArch64/arm64_32.ll | ||
---|---|---|
750 | can you add a test_memset with a nonzero value for the pattern ? |
llvm/test/CodeGen/AArch64/arm64_32.ll | ||
---|---|---|
750 | Wait actually this was tested in arm64-memset-to-bzero.ll which this patch deletes. Why is that ? |
- Fix types for bzero call
- Revert change in test except branching, tailcall now kicks in
llvm/test/CodeGen/AArch64/arm64_32.ll | ||
---|---|---|
754 | The CHECK-DAG: and x0, x0, #0xffffffff should still be tested so I reverted it. bl is changed into a b because we now propagate tailcall for bzero. |
llvm/test/CodeGen/AArch64/arm64_32.ll | ||
---|---|---|
750 | You're right it should not be deleted, only trimmed from the 256 constraint tests. I'll revert it. |
llvm/test/CodeGen/AArch64/arm64-memset-to-bzero.ll | ||
---|---|---|
39–40 | I think we can remove this now. |
I think we can remove this now.