From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org ([63.228.1.57]:35158 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726806AbgCBMos (ORCPT ); Mon, 2 Mar 2020 07:44:48 -0500 Date: Mon, 2 Mar 2020 06:44:42 -0600 From: Segher Boessenkool Subject: Re: eh_frame confusion Message-ID: <20200302124442.GI22482@gate.crashing.org> References: <3b00b45f-74b5-13e3-9a98-c3d6b3bb7286@rasmusvillemoes.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3b00b45f-74b5-13e3-9a98-c3d6b3bb7286@rasmusvillemoes.dk> Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Rasmus Villemoes Cc: LKML , Linux Kbuild mailing list , "linuxppc-dev@lists.ozlabs.org" On Mon, Mar 02, 2020 at 11:56:05AM +0100, Rasmus Villemoes wrote: > I'm building a ppc32 kernel, and noticed that after upgrading from gcc-7 > to gcc-8 all object files now end up having .eh_frame section. Since GCC 8, we enable -fasynchronous-unwind-tables by default for PowerPC. See https://gcc.gnu.org/r259298 . > For > vmlinux, that's not a problem, because they all get discarded in > arch/powerpc/kernel/vmlinux.lds.S . However, they stick around in > modules, which doesn't seem to be useful - given that everything worked > just fine with gcc-7, and I don't see anything in the module loader that > handles .eh_frame. It is useful for debugging. Not many people debug the kernel like this, of course. Segher