public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: cgd@broadcom.com
To: echristo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/5625: exception unwinding creates invalid pointer on mips
Date: Sun, 24 Nov 2002 10:46:00 -0000	[thread overview]
Message-ID: <20021118212602.20217.qmail@sources.redhat.com> (raw)

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

From: cgd@broadcom.com
To: echristo@gcc.gnu.org,
	cgd@broadcom.com,
	echristo@gcc.gnu.org,
	echristo@redhat.com,
	emaste@sandvine.com,
	gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org,
	gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/5625: exception unwinding creates invalid pointer
 on mips
Date: 18 Nov 2002 13:20:32 -0800

 At 18 Nov 2002 20:30:11 -0000, echristo@gcc.gnu.org wrote:
 > Synopsis: exception unwinding creates invalid pointer on mips
 > 
 > State-Changed-From-To: suspended->feedback
 > State-Changed-By: echristo
 > State-Changed-When: Mon Nov 18 12:30:10 2002
 > State-Changed-Why:
 >     Chris,
 >     Can you take a look at this with the mips-rewrite branch please? or did you check your sim changes into the external repository?
 
 All of the relevant sim changes are in the public sim sources.
 
 test with target mipsisa64-elf, target board mips-sim-idt64.
 
 
 chris
 


             reply	other threads:[~2002-11-18 21:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-24 10:46 cgd [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-11 22:47 neroden
2002-11-23 14:16 echristo
2002-11-23 10:06 bkoz
2002-11-01 18:27 bkoz
2002-04-25 19:30 echristo
2002-04-23 12:20 echristo
2002-04-01 11:34 bkoz
2002-02-07 12:06 emaste

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=20021118212602.20217.qmail@sources.redhat.com \
    --to=cgd@broadcom.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).