public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/50906] e500 exception unwinding under "-Os" causes SIGSEGV
Date: Tue, 06 Dec 2011 03:48:00 -0000	[thread overview]
Message-ID: <bug-50906-4-F8BeQodDXc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50906-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #20 from Alan Modra <amodra at gcc dot gnu.org> 2011-12-06 03:47:40 UTC ---
Author: amodra
Date: Tue Dec  6 03:47:37 2011
New Revision: 182040

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=182040
Log:
    PR target/50906
    * config/rs6000/rs6000.c (rs6000_emit_prologue <TARGET_SPE_ABI>):
    Do not mark r11 setup as frame-related.  Pass correct offset to
    rs6000_emit_savres_rtx.  Correct out-of-line rs6000_frame_related
    arguments.  Correct sp_offset.  Remove "offset" fudge from
    in-line rs6000_frame_related call.  Rename misleading variable.
    Fix comments and whitespace.  Tidy some expressions.
    (rs6000_emit_epilogue <TARGET_SPE_ABI>): Always set frame_reg_rtx
    to r11 in out-of-line case.  Correct sp_offset.  Pass correct
    offset to rs6000_emit_savres_rtx.  Rename misleading variable.
    Fix comments and whitespace.  Tidy some expressions.
    (rs6000_emit_epilogue <non-TARGET_SPE_ABI>): Add sp_offset
    adjustment when !saving_GPRs_inline.  Correct register mode
    used in address calcs.
    (rs6000_emit_epilogue <non-TARGET_SPE_ABI>): Similarly when
    !restoring_GPRs_inline.


Modified:
    branches/gcc-4_6-branch/gcc/ChangeLog
    branches/gcc-4_6-branch/gcc/config/rs6000/rs6000.c


  parent reply	other threads:[~2011-12-06  3:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28 20:29 [Bug target/50906] New: " Kyle.D.Moffett at boeing dot com
2011-10-28 20:30 ` [Bug target/50906] " Kyle.D.Moffett at boeing dot com
2011-10-28 20:32 ` Kyle.D.Moffett at boeing dot com
2011-10-28 20:32 ` Kyle.D.Moffett at boeing dot com
2011-11-01 23:44 ` amodra at gmail dot com
2011-11-02  0:06 ` amodra at gmail dot com
2011-11-02 18:24 ` Kyle.D.Moffett at boeing dot com
2011-11-03  4:18 ` amodra at gmail dot com
2011-11-03 12:54 ` amodra at gmail dot com
2011-11-03 12:56 ` amodra at gmail dot com
2011-11-03 12:59 ` amodra at gmail dot com
2011-11-03 16:49 ` Kyle.D.Moffett at boeing dot com
2011-11-04 10:01 ` amodra at gmail dot com
2011-11-04 10:02 ` amodra at gmail dot com
2011-11-04 21:21 ` Kyle.D.Moffett at boeing dot com
2011-11-08 19:28 ` Kyle.D.Moffett at boeing dot com
2011-11-11 10:15 ` dvdkhlng at gmx dot de
2011-11-22 18:57 ` Kyle.D.Moffett at boeing dot com
2011-11-28 20:12 ` Kyle.D.Moffett at boeing dot com
2011-12-06  3:42 ` amodra at gcc dot gnu.org
2011-12-06  3:48 ` amodra at gcc dot gnu.org [this message]
2011-12-06  3:49 ` amodra at gmail 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=bug-50906-4-F8BeQodDXc@http.gcc.gnu.org/bugzilla/ \
    --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).