From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id DA0D73858407; Fri, 24 Sep 2021 07:04:43 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DA0D73858407
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102472] Infinite loop on m68k
Date: Fri, 24 Sep 2021 07:04:43 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 11.2.0
X-Bugzilla-Keywords: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-102472-4-7NmLj0QTmg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-102472-4@http.gcc.gnu.org/bugzilla/>
References: <bug-102472-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2021 07:04:44 -0000

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

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
On the GCC 11 branch head I cannot reproduce this with a x86_64-linux ->
m68k-linux cross cc1, using -O2 -fwrapv -fPIC -g2 -Wno-unused-result
-Wsign-compare -Wall

Can you clarify that it is the compiler that enters an infinite loop rather
than the object being miscompiled and python-uvloop entering an infinite lo=
op?

Can you also please quote the output of the compiler-command when you add -=
v to
the command-line that causes the hang?  In particular the line showing the =
cc1
execution is useful.

Note I did not test GCC 11.2.0 exactly.=