grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Build with -fno-dwarf2-cfi-asm


From: Robert Millan
Subject: Re: [PATCH] Build with -fno-dwarf2-cfi-asm
Date: Thu, 3 Sep 2009 17:38:27 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Thu, Sep 03, 2009 at 04:27:57PM +0100, Colin Watson wrote:
> On Thu, Sep 03, 2009 at 04:47:40PM +0200, Robert Millan wrote:
> > On Thu, Sep 03, 2009 at 11:22:04AM +0100, Colin Watson wrote:
> > > I'd like to commit this for 1.97; it's important for users of recent
> > > distributions that use GCC 4.4 by default (which is the current release
> > > series of GCC). Otherwise, the core is too big to embed when using LVM
> > > and RAID (https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/423412).
> > > Any objections?
> > 
> > Very nice that you found this.  I consider it a bug, and I agree it should
> > be fixed in 1.97.
> > 
> > But shouldn't this be handled by `strip' instead?  IIRC we already do it
> > this way for other unwanted sections.
> 
> I just tried this out. It works in that the image is below 32KB again,
> but it's 30424 bytes rather than the 30331 bytes produced by not
> generating the unwind information in the first place.
> 
> Based on the discussion in the patchwork.kernel.org URL, I think that
> GCC generates unwind information in two places in some cases; only one
> of those corresponds to an ELF section. I'm not terribly familiar with
> the details, though.

Ok.  Unless someone knows better, I'm fine with your previous approach.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."




reply via email to

[Prev in Thread] Current Thread [Next in Thread]