From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 000C23858D26; Thu, 23 May 2024 03:26:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 000C23858D26 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1716434817; bh=HSGAxEl4WqPoz+y2sqQJjZvx3paPh0JfH5wj/sm2G/0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=NSsmhjYPBmqwqs12fsMOVog18UYZhEHVZq625DbtEZOtCdqwtHokwSdms4jqp4Fkz +zXkv8wg04KLRWSUD7Ns56wg4lnVCoidQ+5bQykrzML0PrrJAUkZrHnKbcEVGwIbCA EQKtcJD02phkjrp2R95xMZXywWXG+2s/+PUTwy/0= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115201] Recursion not optimized for structs arguments Date: Thu, 23 May 2024 03:26:56 +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.1.1 X-Bugzilla-Keywords: FIXME, missed-optimization X-Bugzilla-Severity: enhancement X-Bugzilla-Who: pinskia 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: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: keywords see_also 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=3D115201 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |FIXME See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=3D17749 --- Comment #7 from Andrew Pinski --- /* The parameter should be a real operand, so that phi node created for it at the start of the function has the meaning of copying the value. This test implies is_gimple_reg_type from the previous condition, however this one could be relaxed by being more careful with copying the new value of the parameter (emitting appropriate GIMPLE_ASSIGN and updating the virtual operands). */ So this has been a known issue for a long time now.=