Revision 6603a4fd5195a004dec5f9568e38ff76bae630c1 authored by Claudio Scordino on 30 October 2009, 11:06:05 UTC, committed by Russell King on 02 November 2009, 16:59:45 UTC
ARM unwind is known to compile only with EABI and not-buggy compilers. The problem is not the unwinding information but the -fno-frame-pointer option added as a result of !CONFIG_FRAME_POINTER. Now we check the compiler and raise a #warning in case of wrong compiler. Signed-off-by: Claudio Scordino <claudio@evidence.eu.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
1 parent 426fcd2
File | Mode | Size |
---|---|---|
kobject | ||
kprobes | ||
trace_events | ||
tracepoints | ||
Kconfig | -rw-r--r-- | 1.1 KB |
Makefile | -rw-r--r-- | 105 bytes |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...