public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/29997] various targets: GCC fails to encode epilogues in unwind-info
       [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
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu.org @ 2011-12-22  3:53 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-12-22 03:26:11 UTC ---
I think we encode proligue and epilogues now for all targets.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug target/29997] various targets: GCC fails to encode epilogues in unwind-info
       [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
  3 siblings, 0 replies; 6+ messages in thread
From: joseph at codesourcery dot com @ 2011-12-22 12:57 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-12-22 12:53:39 UTC ---
On Thu, 22 Dec 2011, pinskia at gcc dot gnu.org wrote:

> I think we encode proligue and epilogues now for all targets.

It's been done for several targets, but when looking recently I got the 
impression that it hadn't been done yet for SH, for example.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug target/29997] various targets: GCC fails to encode epilogues in unwind-info
       [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
  3 siblings, 0 replies; 6+ messages in thread
From: olegendo at gcc dot gnu.org @ 2013-12-19 16:06 UTC (permalink / raw)
  To: gcc-bugs

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

Oleg Endo <olegendo at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |olegendo at gcc dot gnu.org

--- Comment #5 from Oleg Endo <olegendo at gcc dot gnu.org> ---
Any hints on what is missing or needs to be done for SH?


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug target/29997] various targets: GCC fails to encode epilogues in unwind-info
       [not found] <bug-29997-4@http.gcc.gnu.org/bugzilla/>
                   ` (2 preceding siblings ...)
  2013-12-19 16:06 ` olegendo at gcc dot gnu.org
@ 2013-12-19 16:56 ` ian at airs dot com
  3 siblings, 0 replies; 6+ messages in thread
From: ian at airs dot com @ 2013-12-19 16:56 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #6 from Ian Lance Taylor <ian at airs dot com> ---
All the insns in sh_expand_epilogue need to be examined to see if they need
REG_CFA notes.  Some of them already have them.  I don't know what more are
needed.

For example, look at the changes made to the i386 backend when rth added the
general support for unwinding through epilogues:
http://gcc.gnu.org/ml/gcc-patches/2009-05/msg00277.html


^ 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

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

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