public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/63500] [4.9/5 Regression] bug in debug version of std::make_move_iterator?
Date: Thu, 09 Oct 2014 18:45:00 -0000	[thread overview]
Message-ID: <bug-63500-4-VFZGWkRyEC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63500-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63500

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fdumont at gcc dot gnu.org

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
François, is there a quick fix for this?
>From gcc-bugs-return-463706-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Oct 09 19:01:49 2014
Return-Path: <gcc-bugs-return-463706-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4255 invoked by alias); 9 Oct 2014 19:01:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4216 invoked by uid 55); 9 Oct 2014 19:01:45 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libquadmath/63488] large errors in y0q
Date: Thu, 09 Oct 2014 19:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libquadmath
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63488-4-3T4XN1s2me@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63488-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-10/txt/msg00727.txt.bz2
Content-length: 1884

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc488

--- Comment #8 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Oct 09, 2014 at 06:27:08PM +0000, zimmerma+gcc at loria dot fr wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?idc488
>
> --- Comment #7 from Paul Zimmermann <zimmerma+gcc at loria dot fr> ---
> I agree that near zeroes we can expect large errors. However for
> other functions I got only small errors in ulps, maybe I was unlucky.
> Also the ultimate goal is to get correct rounding, even near zeroes.
>

I suspect you got lucky :-)  IIRC my testing correctly,
exhaustive testing of values in each interval shows
lgammaf(x) for x < 0 and not an integer also has major
accuracy issues:

Interval:                     Max ULP     Value
[-1.10000e+01, -1.00000e+01): 6.72889 -1.0000009e+01
[-1.00000e+01, -9.00000e+00): 83.4928 -9.0000029e+00
[-9.00000e+00, -8.00000e+00): 24615.2 -8.0000248e+00
[-8.00000e+00, -7.00000e+00): 22575.7 -7.9999752e+00
[-7.00000e+00, -6.00000e+00): 100393. -6.0013852e+00
[-6.00000e+00, -5.00000e+00): 36966.5 -5.0082183e+00
[-5.00000e+00, -4.00000e+00): 324309. -4.0393620e+00
[-4.00000e+00, -3.00000e+00): 2981098 -3.1435809e+00
[-3.00000e+00, -2.00000e+00): 7497618 -2.4570248e+00
[-2.00000e+00, -1.00000e+00): 4.18718 -1.7313151e+00
[-1.00000e+00, -4.76837e-07): 3.46651 -3.5002786e-01

troutmask:fvwm:kargl[209] ./testf -a -3.1435809e+00
libm: -2.38418579e-07, 1
mpfr: -1.96054615e-07, 1

The relevant code in testf is (RND is round-to-nearest).

            x = (float)strtof(optarg, NULL);
            y = lgammaf_r(x,&s);
            mpfr_inits2(DBL_MANT_DIG, t1, t2, NULL);
            mpfr_set_d(t1, (double)x, RND);
            mpfr_lgamma(t2, &si, t1, RND);
            printf("libm: %.8e, %d\n", y, s);
            mpfr_printf("mpfr: %.8Re, %d\n", t2, si);
            mpfr_clears(t1, t2, NULL);


  parent reply	other threads:[~2014-10-09 18:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 17:13 [Bug libstdc++/63500] New: " vermaelen.wouter at gmail dot com
2014-10-09 18:17 ` [Bug libstdc++/63500] " glisse at gcc dot gnu.org
2014-10-09 18:36 ` [Bug libstdc++/63500] [4.9/5 Regression] " glisse at gcc dot gnu.org
2014-10-09 18:45 ` redi at gcc dot gnu.org [this message]
2014-10-10 20:37 ` fdumont at gcc dot gnu.org
2014-10-15 20:41 ` fdumont at gcc dot gnu.org
2015-03-11 19:54 ` redi at gcc dot gnu.org

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=bug-63500-4-VFZGWkRyEC@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).