public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "djnz00 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/115019] New: wraparound bug with with -O3 and int128
Date: Fri, 10 May 2024 01:31:50 +0000	[thread overview]
Message-ID: <bug-115019-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 115019
           Summary: wraparound bug with with -O3 and int128
           Product: gcc
           Version: 14.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: djnz00 at gmail dot com
  Target Milestone: ---

Created attachment 58157
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58157&action=edit
reduced testcase

wraparound and condition testing of 128bit values performs incorrectly under
-O3:

  __int128_t i = ((__uint128_t)1)<<127;
  do {
    puts(itoa128(buf, i)); /* do something with i */
    i += ((__uint128_t)1)<<125;
  } while (i);

in other code, this loop runs interminably under -O3, but completes as expected
without optimization; in this reduced testcase sample, it only executes one
repeat of the loop (clang does it correctly); either way, there is a divergence
of behavior with/without -O3

             reply	other threads:[~2024-05-10  1:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10  1:31 djnz00 at gmail dot com [this message]
2024-05-10  1:37 ` [Bug c/115019] " pinskia at gcc dot gnu.org
2024-05-10  1:50 ` pinskia at gcc dot gnu.org
2024-05-10  1:54 ` pinskia 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-115019-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).