From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C44B13849AE7; Fri, 10 May 2024 11:38:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C44B13849AE7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1715341106; bh=Mjtz2awq0ujeC4s8HefVx9jDdzTm+agLSzMJveJxb2o=; h=From:To:Subject:Date:In-Reply-To:References:From; b=AvRpkUbS3xn7DY8QrZ4U1nIHpk/OhVkhHUSguMJ98Ujv2yTyqKQ3YXjNWNeRdia5f aXNaBu0X7Dzs9QrLPIRbpLsGxsh2ow9f28+gGK5kbfwk9WiI2JrjNpvOSPwp8xG4jJ 4EkzRBHnMIVPmgVKIbQPb/Watb2v04tO3WoWD29Y= From: "mdoucha at suse dot cz" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115014] GCC generates incorrect instructions for addressing the data segment through EBP register Date: Fri, 10 May 2024 11:38:26 +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: 13.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: mdoucha at suse dot cz X-Bugzilla-Status: WAITING 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=3D115014 --- Comment #9 from Martin Doucha --- (In reply to Andrew Pinski from comment #8) > Someone in theory could also use an offset from esp and run into a similar > failure. Well yes, but that would be an actual stack overflow and the whole point is= to allow basic protection against that.=