public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Ed Maste <emaste@SANDVINE.com>
To: echristo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: libstdc++/5625: exception unwinding creates invalid pointer o n mips
Date: Wed, 24 Apr 2002 12:46:00 -0000	[thread overview]
Message-ID: <20020424194602.22885.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/5625; it has been noted by GNATS.

From: Ed Maste <emaste@SANDVINE.com>
To: "'cgd@broadcom.com'" <cgd@broadcom.com>, echristo@redhat.com
Cc: Ed Maste <emaste@SANDVINE.com>, "'echristo@gcc.gnu.org'"
	 <echristo@gcc.gnu.org>, "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>, 
	"'gcc-prs@gcc.gnu.org'" <gcc-prs@gcc.gnu.org>, "'gcc-gnats@gcc.gnu.org'"
	 <gcc-gnats@gcc.gnu.org>
Subject: RE: libstdc++/5625: exception unwinding creates invalid pointer o
	 n mips
Date: Wed, 24 Apr 2002 15:41:27 -0400

 > > If _Unwind_Ptr were signed, the right thing should happen.  (iirc; i
 > > seem to recall having discussed this with Ed previously [and him
 > > having confirmed that result, but I may be mistaken].)
 
 That is correct.  
 
 When I discovered the issue I wanted to change as little as possible 
 to isolate it so I left the _Unwind_Ptr typedef alone and rebuilt just
 eh_personality.
 
 -ed


             reply	other threads:[~2002-04-24 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-24 12:46 Ed Maste [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-01 10:36 cgd
2002-04-23 16:16 cgd
2002-04-23 13:56 cgd
2002-04-23 12:56 Eric Christopher
2002-04-23 12:36 Ed Maste

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=20020424194602.22885.qmail@sources.redhat.com \
    --to=emaste@sandvine.com \
    --cc=echristo@gcc.gnu.org \
    --cc=gcc-prs@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).