From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2832A3858C33; Wed, 19 Jul 2023 11:34:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2832A3858C33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1689766499; bh=3/yWmUfbgaZfsEoJxwXGNnNF+Cv9LYSCcOv3Bp/XEzE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=NGfYUJyI3gFvpAlmz9DShU8Zzs9zGbN4GxUVQhcIpTLeh2olOCzFHUVcNeQCN9jWb oT/gFlWmPF727JPSzUb0XmD4mbhTUaTGrSQAGyNWLja36SyjIpd59zr0/F3vsf5ib0 z23L6IFxRu3RshpGW9cgPTiBiiGamO7y7CEh82JY= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110315] [13 Regression] g++ crashes with a segmentation fault while compiling a large const std::vector of std::string since r13-6566-ge0324e2629e25a90 Date: Wed, 19 Jul 2023 11:34: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: 13.1.1 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: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc priority everconfirmed cf_reconfirmed_on bug_status 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=3D110315 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aldyh at gcc dot gnu.org, | |amacleod at redhat dot com Priority|P3 |P2 Ever confirmed|0 |1 Last reconfirmed| |2023-07-19 Status|UNCONFIRMED |NEW --- Comment #2 from Richard Biener --- Confirmed. Not sure whether it's possible to backport any of the stack usa= ge reduction in ranger from trunk or whether it's other recursion limiting that avoids this there (besides different IL from the frontend ...). Andrew/Aldy? The call chain is 20000 frames deep when it faults on me (with a -O0 built cc1plus running in gdb).=