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/85236] missing _mm256_atan2_ps Date: Wed, 03 Apr 2024 19:46:37 +0000 [thread overview] Message-ID: <bug-85236-4-Egv5Npc5zp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-85236-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85236 --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- clang does not implement this intrinsics either and there is no issue filed there about it either (I am kinda of shocked). Note ICX (which is the new ICC but with using clang/LLVM) does and it calls __svml_atan2f8_e9 directly. Looks like SIMD-everywhere has implement it though, see https://github.com/simd-everywhere/simde/issues/40 and https://github.com/simd-everywhere/simde/commit/5b28b3d4672a9cc0616d5d6813b8e31e9bde8148
prev parent reply other threads:[~2024-04-03 19:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-85236-4@http.gcc.gnu.org/bugzilla/> 2024-04-03 19:39 ` pinskia at gcc dot gnu.org 2024-04-03 19:46 ` pinskia at gcc dot gnu.org [this message]
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-85236-4-Egv5Npc5zp@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).