public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
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:28:59 +0000 [thread overview]
Message-ID: <bug-115014-4-v1bgrkG54W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115014-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115014
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #7 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
I think your report was misunderstood. Anyway, when EBP is not a frame pointer,
I think the chances are low that it is derived from ESP. Would accurate
placement of segment override prefixes be worth the effort compared to
prefixing all EBP-relative accesses with DS override?
next prev parent reply other threads:[~2024-05-10 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 15:07 [Bug target/115014] New: " mdoucha at suse dot cz
2024-05-09 15:24 ` [Bug target/115014] " pinskia at gcc dot gnu.org
2024-05-09 15:33 ` mdoucha at suse dot cz
2024-05-09 15:42 ` pinskia at gcc dot gnu.org
2024-05-09 15:58 ` mdoucha at suse dot cz
2024-05-10 3:35 ` xry111 at gcc dot gnu.org
2024-05-10 8:44 ` mdoucha at suse dot cz
2024-05-10 11:28 ` amonakov at gcc dot gnu.org [this message]
2024-05-10 11:33 ` pinskia at gcc dot gnu.org
2024-05-10 11:38 ` mdoucha at suse dot cz
2024-05-10 11:56 ` pinskia at gcc dot gnu.org
2024-05-10 12:11 ` xry111 at gcc dot gnu.org
2024-05-10 12:25 ` mdoucha at suse dot cz
2024-05-10 12:31 ` rguenth at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-115014-4-v1bgrkG54W@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).