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 9407D3858C78; Thu,  4 May 2023 09:53:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9407D3858C78
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1683193980;
	bh=DS3jh4EIgufMUqEQu5orPpEvXMRTitmXHweSTFS7COU=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=MV2msLH7x7fYB3K1p4I/u4O8VIBabPzSMprmTH3256/tPCHnMF/eYJ8uBz2za7K15
	 Qr3MtO7bqSN/FijtnXjLUUR1E1+59WwHH0/8EKDw4gZ1H73TcMvNeImqwKfcKA3+cX
	 xI0Pmv4xFnsG+KUbThnq4kJxOk0j6R69EFPQh3l0=
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109695] [14 Regression] crash in
 gimple_ranger::range_of_expr since r14-377-gc92b8be9b52b7e
Date: Thu, 04 May 2023 09:52:58 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: aldyh at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109695-4-EkRmSCuUQu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109695-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
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #19 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 4 May 2023, aldyh at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109695
>=20
> Aldy Hernandez <aldyh at gcc dot gnu.org> changed:
>=20
>            What    |Removed                     |Added
> -------------------------------------------------------------------------=
---
>                  CC|                            |rguenth at gcc dot gnu.o=
rg
>=20
> --- Comment #16 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
> Is there a way to measure peak memory usage in the compiler?

/usr/bin/time will output maxresident, so that's useful for this.

>  I'd like to
> gather some stats.  Also do we have a handful of programs we typically us=
e to
> measure memory usage?  ISTR that Richard (??) had a set of memory hog pro=
grams.

I gathered testcases from compile-time-hog/memory-hog bugzillas and run
them on an automated tester, nothing more.=