From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org (bombadil.infradead.org [18.85.46.34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 7F806DDE1F for ; Wed, 25 Feb 2009 16:46:49 +1100 (EST) Date: Wed, 25 Feb 2009 00:46:44 -0500 From: Kyle McMartin To: Sam Ravnborg Subject: Re: [PATCH/RFC] powerpc: avoid generating .eh_frame sections with gcc-4.4 Message-ID: <20090225054644.GF6690@bombadil.infradead.org> References: <20090224065112.GA6690@bombadil.infradead.org> <20090225054707.GA20364@uranus.ravnborg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20090225054707.GA20364@uranus.ravnborg.org> Cc: kyle@redhat.com, Kyle McMartin , linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, aoliva@redhat.com, roland@redhat.com List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, Feb 25, 2009 at 06:47:07AM +0100, Sam Ravnborg wrote: > > On ppc64 (at least) gcc-4.4 is defaulting to generating .eh_frame > > sections, which are, for the kernel, fairly pointless. Additionally, on > > ppc64 this generates a relocation format which the kernel module loader > > does not currently support (R_PPC64_REL32.) > > > > Alexandre Oliva verifies that -fno-dwarf2-cfi-asm prevents this > > .eh_frame section from being generated. > > > > These seem to be used for unwinding, but it doesn't look like we > > currently use them anywhere. (In fact, we explicitly dump them in the > > x86_64 linker script.) > > > > If these .eh_frame sections are eventually used, adding a per-arch > > CONFIG_WANT_UNWIND check would be trivial. > > > > (This was reported against Fedora, which appears to be the only distro > > doing any building against gcc-4.4 at present: RH bz#486545.) > > > > Signed-off-by: Kyle McMartin > > Cc: roland@redhat.com > > Cc: aoliva@redhat.com > > Kyle - can you resend wit an updated changelog reflecting the comments > from Roland and Alexandre. > > I got it wrong when reading the above - so chances are others does too. > Yes, certainly. My apologies, I let my frustration leak through a little into the changelog. :) regards, Kyle