[Bug target/29997] [meta-bug] various targets: GCC fails to encode epilogues in unwind-info

[egallager at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29997

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |egallager at gcc dot gnu.org
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=12990

--- Comment #7 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jorn Wolfgang Rennecke from comment #2)
> (In reply to comment #1)
> > I think this is really a dup of bug 12990.
> > 
> 
> Sort of, but not quite.  12990 does no cover the exception handling aspects,
> but it claims that the problem persists target-independently for debug.
> But this is not a problem for ia64.  Since we have now the target-independent
> infrastructure and one target port that uses it to handle this problem,
> this has become a target problem; each target needs to be adjusted separately
> to create the proper epilogue information, so it makes sense to track
> progress (or lack thereof) for each target individually, while having
> one meta-bug to keep track of them all.
> 
> Should I mark 12990 as blocking 29997, and 29998 as blocking 12990?
> 
> OTOH, when you read the description of 12990, it sounds like the problem
> exists only for i[3456]86-*-*, so maybe we should add this to the target
> field of 12990 and only make 12990 as blocking 29997.

Sounds at least related even if not necessarily blocking.