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 506023858D35; Thu, 30 Jul 2020 08:36:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 506023858D35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1596098199;
 bh=BGtWB0DwKlx+8EpHkpzeGR7DS51Bbe1qURZzs7Ncdxc=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=rx5Yh6age0+aIcv9B4Sx4BH+kBP2QlNl7CVCJjNJQIHafGlfVMTRfjptTqboe6bwy
 QviPXIKKUabPyP087bzzcXU5GBXvypVsc0AfFd69M3romh/rEPbf1eJ/uT7sQ5Dg8J
 wwOUAy69CngxIHX7+Ky//B5f9dgH7UmBPedNE5Gk=
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/96388] scheduling takes forever with -fPIC
Date: Thu, 30 Jul 2020 08:36:39 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 11.0
X-Bugzilla-Keywords: compile-time-hog, memory-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-96388-4-TPd6obj4ir@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-96388-4@http.gcc.gnu.org/bugzilla/>
References: <bug-96388-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: Thu, 30 Jul 2020 08:36:39 -0000

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

--- Comment #7 from Martin Li=C5=A1ka <marxin at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #6)
> (In reply to Martin Li=C5=A1ka from comment #5)
> > Started with r9-2469-gc6067437d314f803.
>=20
> Hmm, it probably makes a latent scheduler issue appear.  Guess for better
> analysis we have to trim down the source.  Not sure how - maybe
> automatically with one good and one bad rev. looking for a hundred-fold
> increase in memory use?  Look at the good compile with /usr/bin/time
> and using the RSS to compute a ulimit -v limit or so.

I'm reducing that in the ulimit fence ;) Let see where it leads..=