public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/29997] New: various targets: GCC fails to encode epilogues in unwind-info
@ 2006-11-27 16:28 amylaar at gcc dot gnu dot org
2006-12-02 8:19 ` [Bug target/29997] " pinskia at gcc dot gnu dot org
2006-12-04 14:51 ` amylaar at gcc dot gnu dot org
0 siblings, 2 replies; 6+ messages in thread
From: amylaar at gcc dot gnu dot org @ 2006-11-27 16:28 UTC (permalink / raw)
To: gcc-bugs
See the discussion started with this message:
http://gcc.gnu.org/ml/gcc/2005-10/msg00808.html
According to Jim Wilson in
http://gcc.gnu.org/ml/gcc/2005-10/msg00858.html,
we now have the infrastructure to properly encode prologues / epilogues.
The ia64 port is using this.
--
Summary: various targets: GCC fails to encode epilogues in
unwind-info
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Keywords: wrong-code, meta-bug, EH, wrong-debug
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: amylaar at gcc dot gnu dot org
BugsThisDependsOn: 18749
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29997
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug target/29997] various targets: GCC fails to encode epilogues in unwind-info
2006-11-27 16:28 [Bug target/29997] New: " amylaar at gcc dot gnu dot org
@ 2006-12-02 8:19 ` pinskia at gcc dot gnu dot org
2006-12-04 14:51 ` amylaar at gcc dot gnu dot org
1 sibling, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2006-12-02 8:19 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from pinskia at gcc dot gnu dot org 2006-12-02 08:19 -------
I think this is really a dup of bug 12990.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29997
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug target/29997] various targets: GCC fails to encode epilogues in unwind-info
2006-11-27 16:28 [Bug target/29997] New: " amylaar at gcc dot gnu dot org
2006-12-02 8:19 ` [Bug target/29997] " pinskia at gcc dot gnu dot org
@ 2006-12-04 14:51 ` amylaar at gcc dot gnu dot org
1 sibling, 0 replies; 6+ messages in thread
From: amylaar at gcc dot gnu dot org @ 2006-12-04 14:51 UTC (permalink / raw)
To: gcc-bugs
------- 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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-12-19 16:56 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-29997-4@http.gcc.gnu.org/bugzilla/>
2011-12-22 3:53 ` [Bug target/29997] various targets: GCC fails to encode epilogues in unwind-info pinskia at gcc dot gnu.org
2011-12-22 12:57 ` joseph at codesourcery dot com
2013-12-19 16:06 ` olegendo at gcc dot gnu.org
2013-12-19 16:56 ` ian at airs dot com
2006-11-27 16:28 [Bug target/29997] New: " amylaar at gcc dot gnu dot org
2006-12-02 8:19 ` [Bug target/29997] " pinskia at gcc dot gnu dot org
2006-12-04 14:51 ` amylaar at gcc dot gnu dot org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).