Todd Fiala 0562524b45 On x86 & x86_64, try to use eh_frame for frame 0. ... We decided to use assmbly profiler instead of eh_frame for frame 0 because for compiler generated code, eh_frame is usually synchronous(a.k.a. only valid at call site); and we have no way to tell if it's asynchronous or not. But for x86 & x86_64 compiler generated code: 1. clang & GCC describes all prologue instructions in eh_frame; 2. mid-function stack pointer altering instructions can be easily detected. So we can grab eh_frame, and use assembly profiler to augment it into asynchronous unwind table. This change also benefits hand-written assembly; eh_frame for hand-written assembly is often asynchronous,so we have a much better chance to successfully unwind through them. Change by Tong Shen. llvm-svn: 216406		2014-08-25 20:29:09 +00:00
..
lldb	On x86 & x86_64, try to use eh_frame for frame 0.	2014-08-25 20:29:09 +00:00
Makefile	Merged Eli Friedman's linux build changes where he added Makefile files that	2010-07-09 20:39:50 +00:00