aboutsummaryrefslogtreecommitdiff
path: root/bolt/lib/Utils/CommandLineOpts.cpp
diff options
context:
space:
mode:
authorLang Hames <lhames@gmail.com>2025-10-15 12:21:28 +1100
committerGitHub <noreply@github.com>2025-10-15 12:21:28 +1100
commit8b60c05a7e390a0f06d26c5884aeeb4f3278877c (patch)
treebc325681bdf952ab131d823d28c6ea1ac779a1e7 /bolt/lib/Utils/CommandLineOpts.cpp
parent23848e606baea5c8e5239d56b032399811f54b77 (diff)
downloadllvm-8b60c05a7e390a0f06d26c5884aeeb4f3278877c.zip
llvm-8b60c05a7e390a0f06d26c5884aeeb4f3278877c.tar.gz
llvm-8b60c05a7e390a0f06d26c5884aeeb4f3278877c.tar.bz2
Revert "[ORC] Make runAllocActions and runDeallocActions asynchorous." (#163480)
This reverts commit 3b5842c9c41a441280100045ef62bb8a0fe7200f. The intent of the original commit was to begin enabling asynchronous alloation actions (calls attached to JIT'd memory initialization and deinitialization). The asynchronous allocation actions scheme was fleshed-out in a development branch, but ran into an issue: Functions implementing actions are allowed to live in JIT'd code (e.g. in the ORC runtime), but we can't genally rely on tail-call elimination kicking in. This resulting in dealloc actions returning via stack frames that had been deallocated, triggering segfaults. It's possible that there are other approaches that would allow asynchronous allocation actions to work, but they're not on the critical path for JIT improvements so for now we'll just revert.
Diffstat (limited to 'bolt/lib/Utils/CommandLineOpts.cpp')
0 files changed, 0 insertions, 0 deletions