[all-commits] [llvm/llvm-project] 07deaf: Reland: [llvm][clang] Allocate a new stack instead...

[Michael Spencer via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 07deaf8464f29c34ff46983450a7412a36adcb7b
      https://github.com/llvm/llvm-project/commit/07deaf8464f29c34ff46983450a7412a36adcb7b
  Author: Michael Spencer <bigcheesegs at gmail.com>
  Date:   2025-04-30 (Wed, 30 Apr 2025)

  Changed paths:
    M clang/docs/ReleaseNotes.rst
    M clang/include/clang/Basic/Stack.h
    M clang/lib/Basic/Stack.cpp
    M clang/lib/Frontend/CompilerInstance.cpp
    M llvm/include/llvm/Support/CrashRecoveryContext.h
    A llvm/include/llvm/Support/ProgramStack.h
    M llvm/include/llvm/Support/thread.h
    M llvm/lib/Support/CMakeLists.txt
    M llvm/lib/Support/CrashRecoveryContext.cpp
    A llvm/lib/Support/ProgramStack.cpp
    M llvm/unittests/Support/CMakeLists.txt
    A llvm/unittests/Support/ProgramStackTest.cpp

  Log Message:
  -----------
  Reland: [llvm][clang] Allocate a new stack instead of spawning a new thread to get more stack space (#136046)

Reland https://github.com/llvm/llvm-project/pull/133173

Clang spawns a new thread to avoid running out of stack space. This can
make debugging and performance analysis more difficult as how the
threads are connected is difficult to recover.

This patch introduces `runOnNewStack` and applies it in Clang. On
platforms that have good support for it this allocates a new stack and
moves to it using assembly. Doing split stacks like this actually runs
on most platforms, but many debuggers and unwinders reject the large or
backwards stack offsets that occur. Apple platforms and tools are known
to support this, so this only enables it there for now.



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