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 6FCA2383E800; Mon,  7 Dec 2020 10:38:45 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6FCA2383E800
From: "pmiscml at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/97969] [9/10/11 Regression][ARM/Thumb] Certain combo of
 codegen options leads to compilation infinite loop with growing memory use
Date: Mon, 07 Dec 2020 10:38:45 +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: 10.2.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pmiscml at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.4
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-97969-4-S9CWQR6oaZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-97969-4@http.gcc.gnu.org/bugzilla/>
References: <bug-97969-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: Mon, 07 Dec 2020 10:38:45 -0000

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

--- Comment #11 from Paul Sokolovsky <pmiscml at gmail dot com> ---
In my case, I used the "timeout" command from GNU coreutils. I've attached =
the
actual script used for reference (uncleaned dirty stuff, sorry).

One thing to keep in mind (and which took me a couple of extra creduce runs=
) is
that when it times out, it's the "interesting case" in CReduce terms. And w=
hen
compilation succeeds *or* fails (e.g. because CReduce produced broken synta=
x),
it's "not interesting case". So, you literally need to test for the timeout
exit code vs anything else (be it 0 or 1), like the script shows.=