From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6BC56386F831; Sat, 4 Jul 2020 22:01:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6BC56386F831 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1593900066; bh=yTKh85IO3cqna+4mjYzvpu0XhnoYEK7IN+x53wV7AQI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Kri3mTpgY0Ny1smsZwzIqsKQhHS2MdeRNQsnOwuCB+UEikZPk5FC20Id68NL7JY+9 w8GscR1vJDR8or9OANSH4JwVlYxlqye8Tp8QAdFkr6Gj2RyeOFp6T5fOtIT2W7467V Xk3O6z9xLyjmmx6oP3ixtx8ajwct2lKGRLzPXxDQ= From: "alex.popov at linux dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/96061] Please support 'no_caller_saved_registers' attribute on aarch64 (or maybe on all targets) Date: Sat, 04 Jul 2020 22:01:06 +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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: alex.popov at linux dot com 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: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jul 2020 22:01:06 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96061 --- Comment #6 from Alexander Popov --- >> Could you explain the connection between your attribute for zeroing >> registers and 'no_caller_saved_registers' attribute? >=20 > We are porting >=20 > https://gitlab.com/x86-gcc/gcc/-/tree/users/hjl/caller-saved/old >=20 > from x86 back-end to middle-end. no_caller_saved_registers changes what > registers zero_call_used_regs can do. Move no_caller_saved_registers to > middle-end has a direct impact on zero_call_used_regs implementation in > middle-end. Ok. So, as I can understand, your work will enable 'no_caller_saved_registe= rs' attribute for all architectures. Am I right? If so, good luck to you! Looking forward to your results.=