public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "georgepee at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106763] Armv8.2 vmov.f16 instruction sometimes causes SIGILL
Date: Tue, 30 Aug 2022 14:12:02 +0000 [thread overview]
Message-ID: <bug-106763-4-MEas0QPsn8@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 #4 from George Pee <georgepee at gmail dot com> ---
Yes, it's possible that this isn't a compiler bug. I thought that it might be
because the problem started showing up after upgrading the toolchain.
I wasn't sure if the compiler was failing to emit some kind of alignment or fp
setting code.
I running on linux 4.9.118,
I enabled CONFIG_DEBUG_USER=y and set user_debug=31 in the kernel cmdline.
This is what the kernel reports. I'm starting to look through it.
[ 51.337524] a.out (3638): undefined instruction: pc=00010778
[ 51.337536] CPU: 3 PID: 3638 Comm: a.out Tainted: P O 4.9.118
#2
[ 51.337547] task: 8572b000 task.stack: 8a002000
[ 51.337555] PC is at 0x10778
[ 51.337560] LR is at 0x60dc51b4
[ 51.337567] pc : [<00010778>] lr : [<60dc51b4>] psr: 60000010
[ 51.337567] sp : 72909c50 ip : 60dc51c0 fp : 72909c54
[ 51.337572] r10: 60ff5000 r9 : 00000000 r8 : 00000000
[ 51.337578] r7 : 00000000 r6 : 00010668 r5 : 00000000 r4 : 00003346
[ 51.337583] r3 : 00000000 r2 : 00000001 r1 : 00000000 r0 : 6ff59dd5
[ 51.337589] Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment
user
[ 51.337595] Control: 50c0383d Table: 3e0c406a DAC: 00000015
[ 51.337605] Code: eef81be7 eddf2b05 eec10ba2 eef37b60 (ee173990)
next prev parent reply other threads:[~2022-08-30 14:12 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 [this message]
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
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-MEas0QPsn8@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).