From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E01D63858436; Tue, 27 Feb 2024 15:30:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E01D63858436 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1709047817; bh=Z/4cHJ9ffG0XBrgGZ4Mnj5XPdYvdOqnxSt5UL0Mwg4Y=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nwM77RXORdU2QLtAjxAFgsFuLSrzVq4W4Wd/jfWwLevnYXzSj347gjbsdkMbcZe5C RiJpWlroQdzqzgmq0qH9rnEIp7VfddLVNi07hqE9wRmlHoBk/KCn2ocQYBmTzH14Mv vHnS1p+/ziSWt5ehwn+HKTMXcO+iulw/hvi9CB5s= From: "bergner at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100799] Stackoverflow in optimized code on PPC Date: Tue, 27 Feb 2024 15:30:16 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 10.3.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bergner at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jskumari 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=3D100799 --- Comment #31 from Peter Bergner --- (In reply to Jakub Jelinek from comment #30) > Either tree parmdef =3D ssa_default_def (cfun, parm) is NULL, or has_zero= _uses > (parmdef). > Not sure if has_zero_uses will work properly after some bbs are converted > from GIMPLE to RTL, but maybe it will, I think the expansion generally > doesn't gsi_remove statements it expands nor calls update_stmt on them. = One > could always also just compute in generic code at the start of expansion = the > number of unused DECL_HIDDEN_STRING_LENGTH PARM_DECLs at the end of the > argument list, save that as a flag in struct function or where and let the > backends use it from there. Ok, I think that gives us some idea what needs to be done. I'll look for someone in the team to have a look at implementing this workaround. Thanks= .=