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 o n mips
Date: Wed, 01 May 2002 10:36:00 -0000	[thread overview]
Message-ID: <20020501173601.14999.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@redhat.com,
	"'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>
Cc:  
Subject: Re: libstdc++/5625: exception unwinding creates invalid pointer
 o n mips
Date: 01 May 2002 10:29:36 -0700

 FYI, I just checked in a change to the mips64 gdb simulator code so
 that it will do checking of values (for many, but certainly not all
 8-) which are allowed to produce UNPREDICTABLE results.
 
 This causes 27 gcc (g++, actually) tests which previously passed to
 fail, due to UNPREDICTABLE behaviour:
 
 FAIL: g++.dg/eh/registers1.C execution test
 FAIL: g++.dg/eh/unexpected1.C execution test
 FAIL: g++.brendan/eh1.C  Execution test
 FAIL: g++.eh/flow1.C  Execution test
 FAIL: g++.eh/fntry1.C  Execution test
 FAIL: g++.eh/ia64-1.C  Execution test
 FAIL: g++.eh/inline2.C  Execution test
 FAIL: g++.eh/pdel2.C  Execution test
 FAIL: g++.eh/spec2.C  Execution test
 FAIL: g++.eh/spec3.C  Execution test
 FAIL: g++.eh/spec4.C  Execution test
 FAIL: g++.eh/tmpl1.C  Execution test
 FAIL: g++.mike/eh16.C  Execution test
 FAIL: g++.mike/eh17.C  Execution test
 FAIL: g++.mike/eh33.C  Execution test
 FAIL: g++.mike/eh39.C  Execution test
 FAIL: g++.mike/eh40.C  Execution test
 FAIL: g++.mike/eh49.C  Execution test
 FAIL: g++.mike/eh50.C  Execution test
 FAIL: g++.mike/eh51.C  Execution test
 FAIL: g++.mike/eh6.C  Execution test
 FAIL: g++.other/eh3.C  Execution test
 FAIL: g++.other/singleton.C  Execution test
 FAIL: g++.other/vbase2.C  Execution test
 FAIL: g++.pt/fntry1.C  Execution test
 FAIL: g++.robertl/eb66.C  Execution test
 FAIL: g++.robertl/eb88.C  Execution test
 
 
 
 chris
 
 
 


             reply	other threads:[~2002-05-01 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-01 10:36 cgd [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-24 12:46 Ed Maste
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=20020501173601.14999.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).