Subject: Re: [4.4/4.5 Regression] -g causes GCC to
generate .eh_frame
On Tue, Jun 23, 2009 at 11:09:48AM -0000, jakub at gcc dot gnu dot org wrote:
> I think if we don't want to emit .eh_frame, we should just default to
> -fno-dwarf2-cfi-asm. But if we do want to generate it, I fail to see what do
> we gain by also generating .debug_frame. Duplicating the same info, in one
> case in a more compat form, doesn't look like a good idea.
That sounds reasonable. At one point there was a proposal to emit
completely accurate unwind information for .debug_frame, and skip some
prologue/epilogue information in .eh_frame; if we do that, obviously
we need both sets of output, but otherwise we don't.
We should make this be consistent though, not depend on
-fno-dwarf2-cfi-asm.
Subject: Re: [4.4/4.5 Regression] -g causes GCC to
generate .eh_frame
On Tue, Jun 23, 2009 at 11:09:48AM -0000, jakub at gcc dot gnu dot org wrote: cfi-asm. But if we do want to generate it, I fail to see what do
> I think if we don't want to emit .eh_frame, we should just default to
> -fno-dwarf2-
> we gain by also generating .debug_frame. Duplicating the same info, in one
> case in a more compat form, doesn't look like a good idea.
That sounds reasonable. At one point there was a proposal to emit
completely accurate unwind information for .debug_frame, and skip some
prologue/epilogue information in .eh_frame; if we do that, obviously
we need both sets of output, but otherwise we don't.
We should make this be consistent though, not depend on cfi-asm.
-fno-dwarf2-