------- Comment #2 from amylaar at gcc dot gnu dot org 2006-12-04 14:51 ------- (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. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29997
