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 target/113679] long long minus double with gcc -m32 produces different results than other compilers or gcc -m64 Date: Wed, 31 Jan 2024 08:45:30 +0000 [thread overview] Message-ID: <bug-113679-4-XnNVw4jVL8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113679-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113679 --- Comment #2 from Дилян Палаузов <dilyan.palauzov at aegee dot org> --- This happens only without optimizations: $ gcc -O0 -m32 -o diff diff.c && ./diff -2.000000 $ gcc -O1 -m32 -o diff diff.c && ./diff 0.000000 $ gcc -O2 -m32 -o diff diff.c && ./diff 0.000000 $ gcc -O3 -m32 -o diff diff.c && ./diff 0.000000
next prev parent reply other threads:[~2024-01-31 8:45 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-31 8:40 [Bug c/113679] New: " dilyan.palauzov at aegee dot org 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 [this message] 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-XnNVw4jVL8@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: linkBe 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).