public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7935: floating point test of ">"  fails on -O0, not on -O{1,2,3} for certain values double precision float accessed by operator[] in wrapper class (on ix86)
Date: Tue, 17 Sep 2002 08:56:00 -0000	[thread overview]
Message-ID: <20020917155607.1688.qmail@sources.redhat.com> (raw)

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

From: Richard Henderson <rth@redhat.com>
To: Simon Alexander <sk2alexa@math.uwaterloo.ca>
Cc: rth@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: c++/7935: floating point test of ">"  fails on -O0, not on -O{1,2,3} for certain values double precision float accessed by operator[] in wrapper class (on ix86)
Date: Tue, 17 Sep 2002 08:46:19 -0700

 On Tue, Sep 17, 2002 at 09:12:06AM -0400, Simon Alexander wrote:
 > I am aware of the issues surrounding excess precision.  However, if
 > this is merely a precision issue, can you explain why  it *only* occur
 > when wrapped by a class (not with a raw array), and *only* with -O0 ? 
 
 Your sample set was probably too simple.  With inline accessors, 
 -O0 and a single basic block would be the only time you've got
 a function call between the two computations to force the data
 out of the fp registers.
 
 
 r~


             reply	other threads:[~2002-09-17 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-17  8:56 Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-17  6:16 Simon Alexander
2002-09-16 22:26 rth
2002-09-16 12:26 simon

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=20020917155607.1688.qmail@sources.redhat.com \
    --to=rth@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).