From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 76122382EF0B; Sat, 22 Jun 2024 14:15:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 76122382EF0B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1719065715; bh=byPThcv1JR35JA7/qL7z2jY2wAASMI8Bhim7xMGk5jE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=DP0tmJkC6nXQAEGSxY/KpgrBtBZFURB5vDlhdxeJS7spWmzsLoF41sTHP9VEfkQHo GT2Ws6wWP7RrAaUASpBXbvBFCLDDxEnqP2eRazQPDFhRxic9l4ThftaWxjRUQqrhdL w72MQosEo/ivBoqOC0Np585OYoJOIBbaPiEu6l5g= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115589] (aarch64) clobbered register variables Date: Sat, 22 Jun 2024 14:15:15 +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: 11.4.0 X-Bugzilla-Keywords: inline-asm X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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=3D115589 --- Comment #3 from Andrew Pinski --- Some developers use Local Register Variables in an attempt to improve gcc= =E2=80=99s allocation of registers, especially in large functions. In this case the register name is essentially a hint to the register allocator. While in some instances this can generate better code, improvements are subject to the wh= ims of the allocator/optimizers. Since there are no guarantees that your improvements won=E2=80=99t be lost, this usage of Local Register Variables = is discouraged.=