public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/104544] New: [10/11/12 Regression] '-fcompare-debug' failure (length) w/ -O2
Date: Tue, 15 Feb 2022 07:13:34 +0000	[thread overview]
Message-ID: <bug-104544-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104544
           Summary: [10/11/12 Regression] '-fcompare-debug' failure
                    (length) w/ -O2
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: compare-debug-failure
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: asolokha at gmx dot com
  Target Milestone: ---
            Target: aarch64-linux-gnu

Created attachment 52444
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52444&action=edit
gkd diff

gcc 12.0.1 20220213 snapshot (g:58aeb75d4097010ad9bb72b964265b18ab284f93) fails
-fcompare-debug check when compiling the following testcase w/ -O2:

int m, n;
__int128 q;

void
bar (unsigned __int128 x, int y)
{
  if (x)
    q += y;
}

void
foo (void)
{
  bar (!!q - 1, (m += m ? m : 1) < n);
}

% aarch64-linux-gnu-gcc-12.0.1 -O2 -fcompare-debug -c tod26vmj.c
aarch64-linux-gnu-gcc-12.0.1: error: tod26vmj.c: '-fcompare-debug' failure
(length)

gkd diff attached.

             reply	other threads:[~2022-02-15  7:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  7:13 asolokha at gmx dot com [this message]
2022-02-15  7:21 ` [Bug debug/104544] " pinskia at gcc dot gnu.org
2022-02-15  8:28 ` [Bug rtl-optimization/104544] " rguenth at gcc dot gnu.org
2022-02-15 13:27 ` jakub at gcc dot gnu.org
2022-02-15 13:34 ` jakub at gcc dot gnu.org
2022-02-16 13:50 ` cvs-commit at gcc dot gnu.org
2022-02-16 13:50 ` [Bug rtl-optimization/104544] [10/11 " jakub at gcc dot gnu.org
2022-02-19  8:03 ` cvs-commit at gcc dot gnu.org
2022-02-19  8:09 ` [Bug rtl-optimization/104544] [10 " jakub at gcc dot gnu.org
2022-05-10  8:24 ` cvs-commit at gcc dot gnu.org
2022-06-28 10:48 ` jakub at gcc dot gnu.org
2023-07-07  9:57 ` rguenth 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-104544-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).