[all-commits] [llvm/llvm-project] 8b60c0: Revert "[ORC] Make runAllocActions and runDeallocA...

[Lang Hames via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 8b60c05a7e390a0f06d26c5884aeeb4f3278877c
      https://github.com/llvm/llvm-project/commit/8b60c05a7e390a0f06d26c5884aeeb4f3278877c
  Author: Lang Hames <lhames at gmail.com>
  Date:   2025-10-15 (Wed, 15 Oct 2025)

  Changed paths:
    M llvm/include/llvm/ExecutionEngine/Orc/Shared/AllocationActions.h
    M llvm/lib/ExecutionEngine/JITLink/JITLinkMemoryManager.cpp
    M llvm/lib/ExecutionEngine/Orc/MemoryMapper.cpp
    M llvm/lib/ExecutionEngine/Orc/Shared/AllocationActions.cpp
    M llvm/lib/ExecutionEngine/Orc/TargetProcess/ExecutorSharedMemoryMapperService.cpp

  Log Message:
  -----------
  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.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications