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: Tue, 23 Apr 2002 12:36:00 -0000 [thread overview] Message-ID: <20020423193602.25594.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: "'echristo@gcc.gnu.org'" <echristo@gcc.gnu.org>, "'echristo@redhat.com'" <echristo@redhat.com>, Ed Maste <emaste@SANDVINE.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: Tue, 23 Apr 2002 15:35:33 -0400 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. And then, on page 2: 1.2.1 UNPREDICTABLE UNPREDICTABLE results may vary from processor implementation to implementation, instruction to instruction, or as a function of time on the same implementation or instruction. Software can never depend on results that are UNPREDICTABLE. UNPREDICTABLE operations may cause a result to be generated or not. If a result is generated, it is UNPREDICTABLE. UNPREDICTABLE operations may cause arbitrary exceptions. -ed http://www.mips.com/publications/documentation/MD00087-2B-MIPS64BIS-AFP-00.9 5.pdf (no comma attached to the end of the URL this time!)
next reply other threads:[~2002-04-23 19:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-23 12:36 Ed Maste [this message] 2002-04-23 12:56 Eric Christopher 2002-04-23 13:56 cgd 2002-04-23 16:16 cgd 2002-04-24 12:46 Ed Maste 2002-05-01 10:36 cgd
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=20020423193602.25594.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: linkBe 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).