public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/29997] various targets: GCC fails to encode epilogues in unwind-info
Date: Mon, 04 Dec 2006 14:51:00 -0000	[thread overview]
Message-ID: <20061204145125.25603.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29997-5394@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2006-12-04 14:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]
     [not found] <bug-29997-4@http.gcc.gnu.org/bugzilla/>
2011-12-22  3:53 ` 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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061204145125.25603.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).