94072fbb4e
Using __builtin_frame_address was clever, but didn't work for arm64 (for reasons which were never investigated) and the ChromeOS folks claim it causes trouble for x86 with ARC++ (though without a reproduceable test case). Naked functions turn out to be quite unevenly supported: some architectures do the right thing, others don't; some architectures warn, others don't (and the warnings don't always match the platforms that _actually_ have problems). Inline assembler also removes the guessing games: everyone knows what the couple of instructions _ought_ to be, and now we don't have to reason about what the compiler will actually do (yet still keep the majority of the code in C). Bug: N/A Test: builds, boots Change-Id: I14207ef50ca46b6eca273c3cb7509c311146a3ca |
||
|---|---|---|
| .. | ||
| __bionic_clone.S | ||
| __set_tls.c | ||
| _exit_with_stack_teardown.S | ||
| setjmp.S | ||
| syscall.S | ||
| vfork.S | ||