aboutsummaryrefslogtreecommitdiff
path: root/llvm/unittests/ExecutionEngine/Orc/ExecutionSessionWrapperFunctionCallsTest.cpp
diff options
context:
space:
mode:
authorMikhail R. Gadelha <mikhail@igalia.com>2023-03-27 19:41:39 -0300
committerMikhail R. Gadelha <mikhail@igalia.com>2023-03-27 19:41:54 -0300
commit9b4e8b7b0a6b368dcce474e82bdcd55a2f27bc1e (patch)
tree4fbf7938be702b2c530145f124b8e3604f371872 /llvm/unittests/ExecutionEngine/Orc/ExecutionSessionWrapperFunctionCallsTest.cpp
parent4d64fcdd43a195302de216b57ddb685b1aafe297 (diff)
downloadllvm-9b4e8b7b0a6b368dcce474e82bdcd55a2f27bc1e.zip
llvm-9b4e8b7b0a6b368dcce474e82bdcd55a2f27bc1e.tar.gz
llvm-9b4e8b7b0a6b368dcce474e82bdcd55a2f27bc1e.tar.bz2
[libc] Fix longjmp's fake return in x86_64
This implements the fake return after a successful longjmp(), as described in the linux man page: Following a successful longjmp(), execution continues as if setjmp() had returned for a second time. This "fake" return can be distin- guished from a true setjmp() call because the "fake" return returns the value provided in val. If the programmer mistakenly passes the value 0 in val, the "fake" return will instead return 1. Reviewed By: sivachandra Differential Revision: https://reviews.llvm.org/D146981
Diffstat (limited to 'llvm/unittests/ExecutionEngine/Orc/ExecutionSessionWrapperFunctionCallsTest.cpp')
0 files changed, 0 insertions, 0 deletions