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/105630] New: [10/11/12/13 Regression] '-fcompare-debug' failure w/ -O1 -ftree-parallelize-loops=2
Date: Tue, 17 May 2022 15:24:45 +0000	[thread overview]
Message-ID: <bug-105630-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105630
           Summary: [10/11/12/13 Regression] '-fcompare-debug' failure w/
                    -O1 -ftree-parallelize-loops=2
           Product: gcc
           Version: 13.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

gcc 13.0.0 20220515 snapshot (g:18547874ee205d830acb31f1e3c1c89fc7725c14) fails
-fcompare-debug check when compiling the following testcase w/ -O1
-ftree-parallelize-loops=2:

int m;
static int n;

void
foo (void)
{
  int *arr[] = { &n, &n, &n };
  int unused = n;

  m = 0;
}

void
bar (int *arr, int i)
{
  while (i < 1)
    arr[i++] = 1;
}

aarch64-linux-gnu-gcc-13.0.0 -O1 -fcompare-debug -ftree-parallelize-loops=2 -c
fjosrfpk.c
aarch64-linux-gnu-gcc-13.0.0: error: fjosrfpk.c: '-fcompare-debug' failure

--- fjosrfpk.c.gkd
+++ fjosrfpk.gk.c.gkd
@@ -360,7 +360,7 @@
 1:   int i;
 2:   signed int D.xxxx;

-;; Function bar._loopfn.0 (bar._loopfn.0, funcdef_no=2, cgraph_uid=3,
symbol_order=5)
+;; Function bar._loopfn.0 (bar._loopfn.0, funcdef_no=2, cgraph_uid=3,
symbol_order=6)

 (note # 0 0 NOTE_INSN_DELETED)
 (note # 0 0 [bb 2] NOTE_INSN_BASIC_BLOCK)

It was originally reported in PR105415 comment 8.

             reply	other threads:[~2022-05-17 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 15:24 asolokha at gmx dot com [this message]
2022-05-18 11:49 ` [Bug debug/105630] " jakub at gcc dot gnu.org
2022-05-18 12:37 ` rguenth at gcc dot gnu.org
2022-05-19  9:58 ` cvs-commit at gcc dot gnu.org
2022-05-19  9:59 ` [Bug debug/105630] [10/11/12 " jakub at gcc dot gnu.org
2022-06-28 10:49 ` jakub at gcc dot gnu.org
2023-07-07 10:43 ` [Bug middle-end/105630] [11/12 " 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-105630-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).