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/103788] New: [9/10/11/12 Regression] '-fcompare-debug' failure (length) w/ -O1
Date: Tue, 21 Dec 2021 12:01:05 +0000	[thread overview]
Message-ID: <bug-103788-4@http.gcc.gnu.org/bugzilla/> (raw)

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

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

gcc 12.0.0 20211219 snapshot (g:fcbf94a5be9e0c1ecad92da773a6632b86b7f70a) fails
-fcompare-debug check when compiling the following testcase w/ -O1:

int
bar (void);

int
foo (int x)
{
  int i;

  for (i = 0; i <= __INT_MAX__; ++i)
    x += bar () < (x ? 2 : 1);

  return x;
}

% gcc-12.0.0 -O1 -fcompare-debug -c ohtuq2al.c
gcc-12.0.0: error: ohtuq2al.c: '-fcompare-debug' failure (length)

--- ohtuq2al.c.gkd      2021-12-21 18:49:49.840375354 +0700
+++ ohtuq2al.gk.c.gkd   2021-12-21 18:49:49.891375611 +0700
@@ -75,7 +75,7 @@
         (expr_list:REG_UNUSED (reg:CC 17 flags)
             (nil))))
 (jump_insn # 0 0 3 (set (pc)
-        (label_ref #)) "ohtuq2al.c":10:17# {jump}
+        (label_ref #)) "ohtuq2al.c":10:5# {jump}
      (nil)
  -> 3)
 (barrier # 0 0)

             reply	other threads:[~2021-12-21 12:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 12:01 asolokha at gmx dot com [this message]
2021-12-21 13:57 ` [Bug debug/103788] " marxin at gcc dot gnu.org
2021-12-21 18:44 ` pinskia at gcc dot gnu.org
2021-12-21 18:46 ` pinskia at gcc dot gnu.org
2021-12-21 18:51 ` pinskia at gcc dot gnu.org
2021-12-21 19:00 ` pinskia at gcc dot gnu.org
2021-12-22  4:38 ` asolokha at gmx dot com
2021-12-22  8:42 ` marxin at gcc dot gnu.org
2022-01-18 13:58 ` rguenth at gcc dot gnu.org
2022-01-28 12:23 ` jakub at gcc dot gnu.org
2022-05-27  9:46 ` [Bug debug/103788] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2023-07-07 10:41 ` [Bug debug/103788] [11/12/13/14 " 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-103788-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).