public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernardwidynski at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/111741] New: gcc long double precision
Date: Mon, 09 Oct 2023 17:12:15 +0000	[thread overview]
Message-ID: <bug-111741-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111741
           Summary: gcc long double precision
           Product: gcc
           Version: 11.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bernardwidynski at gmail dot com
  Target Milestone: ---

Created attachment 56081
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56081&action=edit
C program to compute sum of numbers 1, 2, 3, ... N

It is my understanding the long double in gcc has 80 bits precision.

I've run a simple program which shows that it is less than 80 bits precision.

The numbers 1, 2, 3, ... N are summed and compared with N*(N+1)/2

For the case where N = 2^32, the sums compare correctly.

For the case where N = 2^33, the sums are different.

2^33*(2^33-1)/2 is less than 80 bits in precision.

Why doesn't the long double have the capacity for this computation?

See attached program and output file.

This was run on Cygwin64 using gcc version 11.4.0 on an Intel Core i7-9700

             reply	other threads:[~2023-10-09 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 17:12 bernardwidynski at gmail dot com [this message]
2023-10-09 17:12 ` [Bug c/111741] " bernardwidynski at gmail dot com
2023-10-09 17:20 ` pinskia at gcc dot gnu.org
2023-10-09 17:30 ` bernardwidynski at gmail dot com

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-111741-4@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).