public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106763] Armv8.2 vmov.f16 instruction sometimes causes SIGILL Date: Thu, 01 Sep 2022 09:57:11 +0000 [thread overview] Message-ID: <bug-106763-4-XEz0JFF9wI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106763-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106763 --- Comment #11 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- (In reply to George Pee from comment #9) > Using this works around the issue by treating it via a neon path and > enabling the vfp bit and retrying the instruction. > > @@ -824,6 +824,9 @@ call_fpe: > .align 6 > > .LCneon_arm_opcodes: > + .word 0xee000000 @ mask > + .word 0xee000000 @ opcode > + > .word 0xfe000000 @ mask > .word 0xf2000000 @ opcode > > No, that's not going to be the right change (and wouldn't support Thumb, either). I'd start off by trying the following, though it's completely untested: diff --git a/arch/arm/kernel/entry-armv.S b/arch/arm/kernel/entry-armv.S index 0ea8529a4872..df6e3c8533fa 100644 --- a/arch/arm/kernel/entry-armv.S +++ b/arch/arm/kernel/entry-armv.S @@ -629,11 +629,12 @@ call_fpe: #endif ret.w lr @ CP#7 ret.w lr @ CP#8 - ret.w lr @ CP#9 #ifdef CONFIG_VFP + W(b) do_vfp @ CP#9 (VFP) W(b) do_vfp @ CP#10 (VFP) W(b) do_vfp @ CP#11 (VFP) #else + ret.w lr @ CP#9 (VFP) ret.w lr @ CP#10 (VFP) ret.w lr @ CP#11 (VFP) #endif
next prev parent reply other threads:[~2022-09-01 9:57 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-28 14:07 [Bug target/106763] New: " georgepee at gmail dot com 2022-08-28 14:23 ` [Bug target/106763] " georgepee at gmail dot com 2022-08-28 16:15 ` georgepee at gmail dot com 2022-08-30 13:39 ` rearnsha at gcc dot gnu.org 2022-08-30 14:12 ` georgepee at gmail dot com 2022-08-30 14:16 ` rearnsha at gcc dot gnu.org 2022-08-30 14:41 ` georgepee at gmail dot com 2022-08-30 21:11 ` georgepee at gmail dot com 2022-08-31 16:35 ` rearnsha at gcc dot gnu.org 2022-09-01 0:33 ` georgepee at gmail dot com 2022-09-01 9:46 ` rearnsha at gcc dot gnu.org 2022-09-01 9:57 ` rearnsha at gcc dot gnu.org [this message] 2022-09-01 13:22 ` georgepee at gmail dot com 2022-09-01 14:32 ` rearnsha at gcc dot gnu.org 2022-09-01 14:35 ` rearnsha at gcc dot gnu.org 2022-09-01 14:54 ` georgepee at gmail dot com 2022-09-01 14:58 ` rearnsha at gcc dot gnu.org 2022-09-01 15:06 ` georgepee at gmail dot com 2022-09-01 15:14 ` rearnsha 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-106763-4-XEz0JFF9wI@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).