public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/113679] New: long long minus double with gcc -m32 produces different results than other compilers or gcc -m64
Date: Wed, 31 Jan 2024 08:40:21 +0000	[thread overview]
Message-ID: <bug-113679-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113679
           Summary: long long minus double with gcc -m32 produces
                    different results than other compilers or gcc -m64
           Product: gcc
           Version: 13.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dilyan.palauzov at aegee dot org
  Target Milestone: ---

diff.c is:

#include <stdio.h>
int main(void) {
  long long l = 9223372036854775806;
  double d = 9223372036854775808.0;
  printf("%f\n", (double)l - d);
  return 0;
}


With gcc (GCC) 13.2.1 20231205 (Red Hat 13.2.1-6), gcc (Ubuntu
9.4.0-1ubuntu1~20.04.2) 9.4.0, clang 16.0.4 and clang 17.0.5:

$ gcc -m64 -o diff diff.c && ./diff
0.000000
$ gcc -m32 -o diff diff.c && ./diff
-2.000000
$ clang -m64 -o diff diff.c && ./diff
0.000000
$ clang -m32 -o diff diff.c && ./diff
0.000000

With cl.exe 19.29.3015319.29.30153 (first is x84 - 32 bit, second is 64 bit)
C:\> CALL "C:\Program Files (x86)\Microsoft Visual
Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat" x86 10.0.17763.0
C:\> cl diff.c >nul 2>nul & .\diff.exe
0.000000

C:\> CALL "C:\Program Files (x86)\Microsoft Visual
Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat" amd64 10.0.17763.0
C:\> cl diff.c >nul 2>nul & .\diff.exe
0.000000

gcc -m32 produces a different result, compared to gcc -m64, clang 17 (32 and
64bit), and MSCV Visual Studio 2019 (32 and 64bit).

             reply	other threads:[~2024-01-31  8:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31  8:40 dilyan.palauzov at aegee dot org [this message]
2024-01-31  8:44 ` [Bug target/113679] " pinskia at gcc dot gnu.org
2024-01-31  8:45 ` dilyan.palauzov at aegee dot org
2024-01-31  8:52 ` pinskia at gcc dot gnu.org
2024-01-31  8:53 ` jakub at gcc dot gnu.org
2024-01-31  9:58 ` dilyan.palauzov at aegee dot org
2024-01-31 10:02 ` pinskia at gcc dot gnu.org
2024-01-31 10:26 ` jakub at gcc dot gnu.org
2024-01-31 14:32 ` dilyan.palauzov at aegee dot org
2024-01-31 14:35 ` jakub at gcc dot gnu.org
2024-01-31 14:38 ` jakub at gcc dot gnu.org
2024-01-31 15:53 ` jakub at gcc dot gnu.org
2024-02-07  5:55 ` egallager at gcc dot gnu.org
2024-02-10 14:32 ` dilyan.palauzov at aegee dot 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-113679-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).