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/45807] Lying eh_frame r2 save info causes crashes with static libgcc_eh and libstdc++
Date: Tue, 28 Sep 2010 17:14:00 -0000	[thread overview]
Message-ID: <20100928171400.iK_78qBZ3sV1LF36W2PnijVurmOSHSVFR2rCQ5-VUTo@z> (raw)
In-Reply-To: <bug-45807-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Alan Modra <amodra at gcc dot gnu.org> 2010-09-28 15:25:08 UTC ---
Author: amodra
Date: Tue Sep 28 15:25:03 2010
New Revision: 164685

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=164685
Log:
    PR target/45807
    * config/rs6000/aix.h (SETUP_FRAME_ADDRESSES): Delete.
    * config/rs6000/linux64.h (SETUP_FRAME_ADDRESSES): Delete.
    * config/rs6000/rs6000-protos.h (rs6000_aix_emit_builtin_unwind_init):
    Delete.
    * config/rs6000/rs6000.c (rs6000_aix_emit_builtin_unwind_init): Delete.
    (rs6000_emit_prologue): Don't just create frame save info for r2,
    actually save r2.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/rs6000/aix.h
    trunk/gcc/config/rs6000/linux64.h
    trunk/gcc/config/rs6000/rs6000-protos.h
    trunk/gcc/config/rs6000/rs6000.c


  parent reply	other threads:[~2010-09-28 15:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 11:10 [Bug target/45807] New: " amodra at gmail dot com
2010-09-27 14:02 ` [Bug target/45807] " amodra at gmail dot com
2010-09-28 17:14 ` amodra at gcc dot gnu.org [this message]
2010-09-30 21:21 ` meissner at gcc dot gnu.org
2010-10-01  1:52 ` meissner at gcc dot gnu.org
2010-10-01  3:24 ` amodra at gcc dot gnu.org
2010-11-17  6:15 ` amodra at gcc dot gnu.org
2011-11-07  8:07 ` 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=20100928171400.iK_78qBZ3sV1LF36W2PnijVurmOSHSVFR2rCQ5-VUTo@z \
    --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).