public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100382] New: [12 Regression] go.test/test/fixedbugs/issue16095.go hang since r12-248
Date: Sun, 02 May 2021 14:54:12 +0000	[thread overview]
Message-ID: <bug-100382-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 100382
           Summary: [12 Regression] go.test/test/fixedbugs/issue16095.go
                    hang since r12-248
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jakub at gcc dot gnu.org
  Target Milestone: ---

Since r12-248-gb58dc0b803057c0e6032e0d9bd92cd834f72c75c the
go.test/test/fixedbugs/issue16095.go
test hangs.
To reproduce e.g.:
../configure --enable-languages=c,c++,go --disable-bootstrap
make -j32
cd gcc
make -j32 check-go
The first difference (good to bad) is in the dse2 dump:
@@ -889,7 +889,6 @@ void main.main ()
   uint8[20] * _69;
   uint32 _72;
   uint64 GOTMP.131_73;
-  int _74;
   bool GOTMP.132_75;
   bool GOTMP.132_77;
   int GOTMP.16_155;
@@ -1190,7 +1189,6 @@ void main.main ()
   goto <bb 52>; [100.00%]

   <bb 54> [count: 0]:
-  _74 = MEM[(int *)0B];
   goto <bb 54>; [100.00%]

   <bb 55> [count: 0]:
@@ -1217,7 +1215,7 @@ void main.main ()
   goto <bb 68>; [100.00%]

   <bb 59> [count: 0]:
-  # x_76 = PHI <x_78(D)(36), _61(37), _61(41), _61(44), _61(45), _61(46),
_61(47), _61(48), _61(53), _61(54)>
+  # x_76 = PHI <x_78(D)(36), _61(37), _61(41), _61(44), _61(45), _61(46),
_61(47), _61(48), _61(53)>
 <L28>:
   # DEBUG x => x_76
   runtime.checkdefer (&GOTMP.15);

             reply	other threads:[~2021-05-02 14:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02 14:54 jakub at gcc dot gnu.org [this message]
2021-05-02 14:54 ` [Bug tree-optimization/100382] " jakub at gcc dot gnu.org
2021-05-02 17:46 ` jakub at gcc dot gnu.org
2021-05-03  6:51 ` rguenth at gcc dot gnu.org
2021-05-03  7:13 ` rguenth at gcc dot gnu.org
2021-05-03 10:04 ` cvs-commit at gcc dot gnu.org
2021-05-03 10:12 ` jakub at gcc dot gnu.org
2021-10-25 12:09 ` cvs-commit 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-100382-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).