public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "john_platts at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113484] New: Add support for _Float16 type on PowerPC Date: Thu, 18 Jan 2024 14:14:53 +0000 [thread overview] Message-ID: <bug-113484-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113484 Bug ID: 113484 Summary: Add support for _Float16 type on PowerPC Product: gcc Version: 12.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: john_platts at hotmail dot com Target Milestone: --- POWER9 has instructions for _Float16 to float, _Float16 to double, float to _Float16, and double to _Float16 conversions, but the _Float16 type is not currently supported on POWER9 platforms. There are also currently no intrinsics available for the POWER9 _Float16 to double (xscvhpdp) and double to _Float16 (xscvdphp) instructions on GCC. GCC does have intrinsics for POWER9 _Float16 vector to float vector (xvcvhpsp) and float vector to _Float16 vector (xvcvsphp) instructions, but the vec_extract_fp32_from_shorth, vec_extract_fp32_from_shortl, and vec_pack_to_short_fp32 intrinsics use __vector unsigned short to represent _Float16 values. Adding support for _Float16 on POWER9 would allow conversions between _Float64 and double to be done using casts instead of having to resort to inline assembly.
next reply other threads:[~2024-01-18 14:14 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-18 14:14 john_platts at hotmail dot com [this message] 2024-01-18 20:13 ` [Bug target/113484] " pinskia at gcc dot gnu.org 2024-01-18 21:08 ` jsm28 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-113484-4@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).