On 04/03/2020 21:45, Jim Ingham via llvm-dev wrote:
> As you have seen, different machine architectures do different things after
> hitting a trap. On x86_64, the trap instruction is executed, and then you
> stop, so the PC is left after the stop. On arm64, when execution halts the
> pc is sti
As you have seen, different machine architectures do different things after
hitting a trap. On x86_64, the trap instruction is executed, and then you
stop, so the PC is left after the stop. On arm64, when execution halts the pc
is still pointing at the trap instruction.
I don't think lldb sho
Hi,
I'm noticing an unexpected difference between targets when I hit a dbgtrap in
the debugger. Consider this simple llvm function:
define void @do_break() {
entry:
call void @llvm.debugtrap()
ret void
}
If I compile that with llc and use lldb to launch a program that calls it, on
x
Hello everyone,
It took a bit longer than planned, but Release Candidate 3 is now
here. It was tagged as llvmorg-10.0.0-rc3 on the release branch at
3a843031a5 and contains 95 commits since the previous release
candidate.
If no new problems arise, this is what the final release will look like.
S
