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/99217] [MIPS] wrong function entry with -fpatchable-function-entry
Date: Tue, 23 Feb 2021 19:44:42 +0000 [thread overview]
Message-ID: <bug-99217-4-o4RiVVLZTl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99217-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99217
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Component|c |target
Keywords| |wrong-code
Last reconfirmed| |2021-02-23
Target| |mips*-linux-gnu
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.
.globl f
.section __patchable_function_entries,"aw",@progbits
.align 3
.8byte .LPFE1
.text
.LPFE1:
.set noreorder
nop
.set reorder
.set noreorder
nop
.set reorder
.set noreorder
nop
.set reorder
.LFB0 = .
.cfi_startproc
.set nomips16
.set nomicromips
.ent f
.type f, @function
f:
---- CUT ---
AARCH64 does:
f:
.section __patchable_function_entries,"aw",@progbits
.align 3
.8byte .LPFE1
.text
.LPFE1:
nop
nop
nop
.LFB0:
next prev parent reply other threads:[~2021-02-23 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 11:37 [Bug c/99217] New: " huangpei at loongson dot cn
2021-02-23 19:44 ` pinskia at gcc dot gnu.org [this message]
2021-03-04 2:07 ` [Bug target/99217] " huangpei at loongson dot cn
2021-03-04 3:20 ` pinskia at gcc dot gnu.org
2021-03-05 7:22 ` huangpei at loongson dot cn
2021-12-04 7:54 ` huangpei at loongson dot cn
2021-12-15 10:00 ` huangpei at loongson dot cn
2021-12-15 10:01 ` huangpei at loongson dot cn
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-99217-4-o4RiVVLZTl@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).