From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7C3A53858D33; Fri, 2 Feb 2024 00:31:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7C3A53858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706833900; bh=XN1k9y4xPPwjzFqeXMDIaQ7Ua/pAl6dkaJIjVgbxGJY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=FY9IyCpGz+Wk8E8mOcFDfhOvWOz530X+3VLQjceuYvFF5R8Y15s9uBZdB3t6rPODU lkOozxhIi51yMhr3pL0vl0/uiDbOCE0VZQfe8VVc8NqqJhCFxPcseE/77tiMA9mxAF RbA08Sv1T/ERSWNspo15zwHbcZHISgU9ao/z6bIA= From: "matheus.a.m.moreira at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113694] Allow renaming stack smashing protector symbols Date: Fri, 02 Feb 2024 00:31:38 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: matheus.a.m.moreira at gmail dot com X-Bugzilla-Status: UNCONFIRMED 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113694 --- Comment #2 from Matheus Afonso Martins Moreira --- That's true but in that case the __stack_chk_* symbols will remain in the compiler output and in the final binary. They will show up in readelf outpu= t, GDB function disassemblies. I think the ability to rename the symbols would be a cleaner solution. Programmers should have full control over the symbols emitted by the compil= er.=