public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Possible Math Problem - Request For Verification [Solved]
Date: Sat, 25 Jun 2011 20:54:10 -0700	[thread overview]
Message-ID: <BANLkTim7kf_=YKBvvZ5w4Pq67rtCgVfXyw@mail.gmail.com> (raw)
In-Reply-To: <20110625234418.a66f8d7b.frank.peters@comcast.net>

On Sat, Jun 25, 2011 at 8:44 PM, Frank Peters <frank.peters@comcast.net> wrote:
> On Sat, 25 Jun 2011 13:41:11 -0400
> Frank Peters <frank.peters@comcast.net> wrote:
>
>>
>> /tmp/fp-test-results/clib_DP.output: ucbtest UCBFAIL in cabsd at line 701 for double
>>
>
> The culprit seems to be GCC optimization.  If I run the test with either "-O0"
> or "-O1" flags I can eliminate the cabsd failure.  Using "-O2" or "-O3" will
> result in the cabsd error.
>
> However, I've used "-O2" previously and had no problems with this test.  Possibly,
> some of these new LTO and GRAPHITE capabilities of GCC are to blame, even though
> I do not compile the ucbtest with either LTO or GRAPHITE enabled.  But GCC has itself
> been compiled using LTO and GRAPHITE.
>
> Anyway, thanks for all who actually ran the test on their machines.  I was
> thinking of filing bug reports with GLIBC and GCC and that would have turned
> out to be foolish.  I did check the Changelogs for GLIBC and there doesn't seem
> to have been any modification of the cabs() code over the last several versions.
>
> Frank Peters

I'm using -O2 here on all my machines. Certainly it isn't that option
that causes a problem for everyone. Sounds like something specific to
your processor revision.

Take care,
Mark



  reply	other threads:[~2011-06-26  3:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-25 17:41 [gentoo-amd64] Possible Math Problem - Request For Verification Frank Peters
2011-06-25 23:54 ` Marc Joliet
2011-06-26  0:22   ` Mark Knecht
2011-06-26  1:10     ` Frank Peters
2011-06-26  1:28   ` Frank Peters
2011-06-26  3:44 ` [gentoo-amd64] Possible Math Problem - Request For Verification [Solved] Frank Peters
2011-06-26  3:54   ` Mark Knecht [this message]
2011-06-26  4:39     ` Frank Peters
2011-06-26 11:33       ` James Cloos
2011-06-26 12:57       ` Mark Knecht
2011-06-26 16:30       ` Barry Schwartz
2011-06-26 11:30 ` [gentoo-amd64] Possible Math Problem - Request For Verification Volker Armin Hemmann
2011-06-26 12:13   ` Volker Armin Hemmann
2011-06-26 13:17     ` [gentoo-amd64] unsubscribe Piotr Hosowicz
2011-06-26 15:40       ` Dale
2011-06-26 17:26         ` Lie Ryan
2011-06-26 17:31           ` Volker Armin Hemmann
2011-06-26 17:52             ` Dale
2011-06-27  3:22             ` [gentoo-amd64] unsubscribe Duncan
2011-06-26 17:43           ` [gentoo-amd64] unsubscribe Dale
2011-06-26 16:27   ` [gentoo-amd64] Possible Math Problem - Request For Verification Frank Peters
2011-06-26 17:04 ` Volker Armin Hemmann
2011-06-26 17:17   ` Mark Knecht
2011-06-26 17:36   ` Frank Peters
2011-06-26 17:45     ` Volker Armin Hemmann
2011-06-26 17:54     ` Barry Schwartz
2011-06-26 19:01     ` Volker Armin Hemmann
2011-06-26 19:21       ` Barry Schwartz
2011-06-26 19:31         ` Volker Armin Hemmann
2011-06-26 19:49         ` Mark Knecht
2011-06-26 20:33           ` Frank Peters

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='BANLkTim7kf_=YKBvvZ5w4Pq67rtCgVfXyw@mail.gmail.com' \
    --to=markknecht@gmail.com \
    --cc=gentoo-amd64@lists.gentoo.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