public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jeffhurchalla at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98474] incorrect results using __uint128_t Date: Tue, 29 Dec 2020 22:17:14 +0000 [thread overview] Message-ID: <bug-98474-4-a6n4MLcdu9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98474-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98474 --- Comment #1 from Jeff Hurchalla <jeffhurchalla at gmail dot com> --- If I change only the optimization level in the compile command to -O1, then echo prints the correct result 0. I have a non-minimal (but still very small) test file on godbolt at https://godbolt.org/z/4oqnYn The godbolt link goes to two separate tests which produce the incorrect results - you can toggle between them with the "#if 1". There are two interesting things about the godbolt tests: 1. I get correct results when I choose "x86_64 gcc 4.9.3" and incorrect results when I choose "x86_64 gcc 5.1". The few earlier versions than 4.9.3 that I tried were correct also, and the few later versions than 5.1 (including trunk) that I tried were incorrect also. 2. Using "x86_64 gcc 10.2" (and I'd suspect any version >= 5.1), the tests print to stdout "inside 'if'" but they do not print "inside 'while'" This should be impossible.
next prev parent reply other threads:[~2020-12-29 22:17 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-29 21:57 [Bug c++/98474] New: " jeffhurchalla at gmail dot com 2020-12-29 22:17 ` jeffhurchalla at gmail dot com [this message] 2020-12-29 22:27 ` [Bug tree-optimization/98474] [8/9/10/11 Regression] " jakub at gcc dot gnu.org 2020-12-29 22:27 ` jakub at gcc dot gnu.org 2020-12-30 10:03 ` jakub at gcc dot gnu.org 2020-12-31 2:59 ` jeffhurchalla at gmail dot com 2020-12-31 10:07 ` cvs-commit at gcc dot gnu.org 2020-12-31 10:11 ` [Bug tree-optimization/98474] [8/9/10 " jakub at gcc dot gnu.org 2021-01-01 2:44 ` jeffhurchalla at gmail dot com 2021-01-05 10:44 ` rguenth at gcc dot gnu.org 2021-01-06 9:40 ` cvs-commit at gcc dot gnu.org 2021-01-06 9:46 ` [Bug tree-optimization/98474] [8/9 " jakub at gcc dot gnu.org 2021-04-20 23:31 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:49 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:09 ` jakub 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-98474-4-a6n4MLcdu9@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).