From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 25CF83857722; Mon, 15 May 2023 22:27:01 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 25CF83857722 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684189621; bh=MS77jEF1vh8W2w+fMzZd0LoUZX4QGfT9LspFl38oP8g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=rZ23d/3WZjIBTYhSZ5gKP/qN4YiE5dMMewkTnROpNsb6EWyk3gQZBArr8LHKQByN/ xNhgFfBwWlKGhnZGbcX9jK9zqDbZVffDYqs1cTjLpYbECf3GgDf/zVQmc+Ko1nEUJh 8deq6Cr3k91eu7poJilqIrEdoRifX3ec5DaYd55k= From: "amonakov at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109806] [13/14 Regression] 13.1.0 cc1plus stack smashing crash with C array of complex structs Date: Mon, 15 May 2023 22:27:00 +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.0 X-Bugzilla-Keywords: ice-on-valid-code, memory-hog X-Bugzilla-Severity: critical X-Bugzilla-Who: amonakov 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: 13.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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=3D109806 Alexander Monakov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amonakov at gcc dot gnu.org --- Comment #13 from Alexander Monakov --- The 128KB stack size is for *secondary* threads on musl (i.e. those created= via pthread_create). The main thread has the same stack as on glibc (GCC extend= s it to 128MB unless there's a hard limit). This doesn't look like a stack exhaustion and should be a separate bug.=