From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C75D1385B53E; Fri, 12 May 2023 19:30:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C75D1385B53E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683919828; bh=cwZwhGS3NjfOep73Yo2oaKwAOSr9uemZKElN8kA3kIY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=j2T0FJy9eVW1inD6I31B4MS4D2IHYJYwORV8jkzeoAhxuSgCDh5z1Alc+BvWjD8hZ WQg4IaUUI1b4X12/Yi9CShtHiCvnR4fTvP4zKQMln5krFF51Mp78B+GnMVMCWBmrK9 BgPHE512C62MDVgtKfB4yon0lWsr692w1N4/Ar78= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106943] GCC building clang/llvm with LTO flags causes ICE in clang Date: Fri, 12 May 2023 19:30:28 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 12.2.0 X-Bugzilla-Keywords: ice-on-valid-code, needs-reduction X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: WAITING 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: 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=3D106943 --- Comment #27 from Andrew Pinski --- (In reply to Alexander Monakov from comment #26) > Would that help? GCC raises its own stack limit to 64MB: >=20 > gcc.cc: stack_limit_increase (64 * 1024 * 1024); > toplev.cc: stack_limit_increase (64 * 1024 * 1024); Oh I forgot about that.=