diff options
| author | Nick Desaulniers <nickdesaulniers@users.noreply.github.com> | 2024-03-26 08:27:43 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-03-26 08:27:43 -0700 |
| commit | ecfffbfd3921fd47f3afc1d03a7518b34ec396b3 (patch) | |
| tree | bb22e3eb00f8d4566145666af19083a32e48c2c4 /clang/lib/CodeGen/CodeGenFunction.cpp | |
| parent | d18bee2313ab8274fad386b1c0227316bf4238b2 (diff) | |
| download | llvm-ecfffbfd3921fd47f3afc1d03a7518b34ec396b3.zip llvm-ecfffbfd3921fd47f3afc1d03a7518b34ec396b3.tar.gz llvm-ecfffbfd3921fd47f3afc1d03a7518b34ec396b3.tar.bz2 | |
[libc][OSUtil] refactor quick_exit to be an object library everywhere (#85955)
The usage of __builtin_unreachable after calls to quick_exit were distressing.
If a function is properly marked [[noreturn]] then __builtin_unreachable is not
necessary.
Looking into this further, we seem to have header only implementations for CPU
targets. The inline nature of these functions is curious; we're going to exit,
it doesn't matter if we need to pay the call of a function or not. If we just
make these functions have distinct TUs rather than be header only, we can clean
up the cmake rules for quick_exit which were different between CPU and GPU.
Remove darwin support for quick_exit. This isn't being tested, and we can bring
it back when necessary.
Diffstat (limited to 'clang/lib/CodeGen/CodeGenFunction.cpp')
0 files changed, 0 insertions, 0 deletions