public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Eric Christopher <echristo@redhat.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: Tue, 23 Apr 2002 12:56:00 -0000	[thread overview]
Message-ID: <20020423195601.4795.qmail@sources.redhat.com> (raw)

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

From: Eric Christopher <echristo@redhat.com>
To: Ed Maste <emaste@SANDVINE.com>
Cc: "'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: 23 Apr 2002 12:44:46 -0700

 On Tue, 2002-04-23 at 12:35, Ed Maste wrote:
 > Yes, the MIPS documentation states that the destination register 
 > gets the sign-extended result ("GPR[rt]<-sign_extend(temp31..0)").
 > 
 > However, note the ADDIU instruction Restrictions section:
 > 
 >      Restrictions:
 >      If GPR rs does not contain a sign-extended 
 >      32-bit value (bits 63..31 equal), then the 
 >      result of the operation is UNPREDICTABLE.
 > 
 
 So it sounds like both your processor and gcc are in error. gcc by not
 sign extending the value before and you for not sign extending it after.
 
 I'll take a look at the sign extension requirements in the back end.
 
 -eric
 
 -- 
 A fire drill does not demand
 a fire.
 


             reply	other threads:[~2002-04-23 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 12:56 Eric Christopher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-01 10:36 cgd
2002-04-24 12:46 Ed Maste
2002-04-23 16:16 cgd
2002-04-23 13:56 cgd
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=20020423195601.4795.qmail@sources.redhat.com \
    --to=echristo@redhat.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).