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 07395385ED4B; Thu, 30 Jul 2020 08:34:42 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 07395385ED4B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1596098082;
 bh=B+5rrOpiK/h810mqLICFkq/A9UnAC+Z5sczaaPKtTWI=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=DRhIF3JS3yc/MwJ33ZkgTH7EMqlObz1NP2uXAv6F8nFXZvd9fs6f7WUS6vv3LUzts
 TwytpbYzvreLbfyqv9ySJcloA7JUlpO/M9BngyHyVmt4q18OeboR5cFJWlYpO1RAEm
 Q80b3kbstfBjPM1b0E2sOE2yaN2x57QmFz7tPDaE=
From: "rguenth 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:34:41 +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: rguenth 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-iBqF0lOhLT@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:34:42 -0000

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

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Martin Li=C5=A1ka from comment #5)
> Started with r9-2469-gc6067437d314f803.

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.=