public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/48227] "rep ret" generated for -march=core2 Date: Wed, 29 Dec 2021 04:12:06 +0000 [thread overview] Message-ID: <bug-48227-4-rddHVBXTSr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48227-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48227 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Target Milestone|--- |8.0 See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=81616 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- /* X86_TUNE_PAD_RETURNS: Place NOP before every RET that is a destination of conditional jump or directly preceded by other jump instruction. This is important for AND K8-AMDFAM10 because the branch prediction architecture expect at most one jump per 2 byte window. Failing to pad returns leads to misaligned return stack. */ DEF_TUNE (X86_TUNE_PAD_RETURNS, "pad_returns", m_ATHLON_K8 | m_AMDFAM10) Core2 issue was Fixed by r0-125351 for 4.9.0. GCC 8 removed it even for generic by r8-5077. So all fixed.
prev parent reply other threads:[~2021-12-29 4:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-22 9:10 [Bug target/48227] New: " zuxy.meng at gmail dot com 2011-04-01 19:21 ` [Bug target/48227] " pinskia at gcc dot gnu.org 2011-04-02 0:55 ` ian at airs dot com 2011-04-06 13:42 ` zuxy.meng at gmail dot com 2011-12-15 23:23 ` pinskia at gcc dot gnu.org 2021-12-29 4:12 ` pinskia at gcc dot gnu.org [this message]
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-48227-4-rddHVBXTSr@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: linkBe 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).