public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105339] [x86] missing AVX-512F scalef functions when optimization is disabled
Date: Fri, 22 Apr 2022 03:07:52 +0000 [thread overview]
Message-ID: <bug-105339-4-j6AxLyknby@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105339-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105339
Hongtao.liu <crazylht at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |crazylht at gmail dot com
--- Comment #1 from Hongtao.liu <crazylht at gmail dot com> ---
Hmm
3316#define _mm_mask_scalef_sd(W, U, A, B) \
3317 _mm_mask_scalef_round_sd ((W), (U), (A), (B),
_MM_FROUND_CUR_DIRECTION)
3318
3319#define _mm_maskz_scalef_sd(U, A, B) \
3320 _mm_maskz_scalef_round_sd ((U), (A), (B), _MM_FROUND_CUR_DIRECTION)
3321
3322#define _mm_mask_scalef_ss(W, U, A, B) \
3323 _mm_mask_scalef_round_ss ((W), (U), (A), (B),
_MM_FROUND_CUR_DIRECTION)
3324
3325#define _mm_maskz_scalef_ss(U, A, B) \
3326 _mm_maskz_scalef_round_ss ((U), (A), (B), _MM_FROUND_CUR_DIRECTION)
they're defined as macros, but _mm_maskz_scalef_round_ss is only available
under __OPTIMIZE__.
next prev parent reply other threads:[~2022-04-22 3:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 0:46 [Bug target/105339] New: " evan@coeus-group.com
2022-04-22 3:07 ` crazylht at gmail dot com [this message]
2022-04-22 3:14 ` [Bug target/105339] " crazylht at gmail dot com
2022-04-25 1:18 ` cvs-commit at gcc dot gnu.org
2022-04-27 7:15 ` cvs-commit at gcc dot gnu.org
2022-04-27 7:16 ` cvs-commit at gcc dot gnu.org
2022-04-27 7:20 ` cvs-commit at gcc dot gnu.org
2022-04-27 7:20 ` wwwhhhyyy333 at gmail dot com
2022-12-19 22:50 ` pinskia 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-105339-4-j6AxLyknby@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).