From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 65E7C3858C53; Tue, 9 May 2023 13:01:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 65E7C3858C53 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683637284; bh=n2IBdR9DVbEFQYI9RYTVvPxhr8CylKrp08gzBOXHT0M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hetwB7uXpMJfxN0j9ICkTY/IlE2K2HT3n/F3MP6/RV4CJGLLLyorIT6AjaaBpGsmB PRs/IzvgD4njAodEG1tnXRHCyLbu0JB66/gAj8YBz27bq3K6PEOMGd6vm71rYHn6XJ WQAbfMzuwquMZdnxwPhKqF+hxCAmlU2WUTPVjnss= From: "rguenth at gcc dot 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: Tue, 09 May 2023 13:01:24 +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: rguenth at gcc dot gnu.org 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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109695 --- Comment #25 from Richard Biener --- (In reply to Aldy Hernandez from comment #24) > FYI. I originally tried new/delete for allocation, which was a tad slower > than ggc_alloc / ggc_free. Not too much, but measurable. >=20 > Another idea would be to have a global obstack which auto_int_range<> use= s, > which gets freed at the end of every pass. This saves us various > ggc_free()s throughout, especially at destruction. I think ggc_{alloc,free} is a no-go. For now I'd go with new/delete, the choice of N should be so that we do not get allocation in >90% of the cases anyway.=