ARC: unwind: ensure that .debug_frame is generated (vs. .eh_frame)
authorVineet Gupta <vgupta@synopsys.com>
Tue, 28 Jun 2016 04:12:25 +0000 (09:42 +0530)
committerSasha Levin <sasha.levin@oracle.com>
Mon, 11 Jul 2016 02:27:12 +0000 (22:27 -0400)
commit7678c949a43aefb98ac7e64d6b8b2c32ad442fc3
treeed31a2b0748151215bd7a04468e95ab64faa1809
parent7421921581dc77ffb4017ce747f95931f74a624b
ARC: unwind: ensure that .debug_frame is generated (vs. .eh_frame)

[ Upstream commit f52e126cc7476196f44f3c313b7d9f0699a881fc ]

With recent binutils update to support dwarf CFI pseudo-ops in gas, we
now get .eh_frame vs. .debug_frame. Although the call frame info is
exactly the same in both, the CIE differs, which the current kernel
unwinder can't cope with.

This broke both the kernel unwinder as well as loadable modules (latter
because of a new unhandled relo R_ARC_32_PCREL from .rela.eh_frame in
the module loader)

The ideal solution would be to switch unwinder to .eh_frame.
For now however we can make do by just ensureing .debug_frame is
generated by removing -fasynchronous-unwind-tables

 .eh_frame    generated with -gdwarf-2 -fasynchronous-unwind-tables
 .debug_frame generated with -gdwarf-2

Fixes STAR 9001058196

Cc: stable@vger.kernel.org
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
arch/arc/Makefile