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 14:58:30 +0000 [thread overview]
Message-ID: <bug-106763-4-c5VlnL34bR@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 #16 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to George Pee from comment #15)
> Funny that you mention that...
> https://lore.kernel.org/linux-arm-kernel/20220901141307.2361752-1-
> georgepee@gmail.com/T/#u
:)
Don't forget that the arm64 kernel will also need to export the same HWCAP
values when supporting a 32-bit userland.
next prev parent reply other threads:[~2022-09-01 14:58 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
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 [this message]
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-c5VlnL34bR@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).