public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109504] [12/13 Regression] Compilation fails with pragma GCC target sse4.1 and immintrin.h Date: Fri, 14 Apr 2023 08:01:32 +0000 [thread overview] Message-ID: <bug-109504-4-v0y3HSN0Qs@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109504-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109504 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Yeah. Enable all the time and have say the targetm.invalid_conversion, targetm.invalid_unary_op, targetm.invalid_binary_op and something in argument/return value passing reject _Float16/__bf16 in functions without SSE2. That will not be enough though, we'll need to arrange e.g. for the spot where we #undef/#define target macros based on currently active ISA in pragmas to also do that for __STDCPP_FLOAT16_T__ and __STDCPP_BFLOAT16_T__ for C++, and change libstdc++ such that for x86 it adds similarly to x86 intrin headers something like #ifndef __SSE2__ #pragma GCC push_options #pragma GCC target("sse2") #define __DISABLE_SSE2__ #endif /* __SSE2__ */ ... #ifdef __DISABLE_SSE2__ #undef __DISABLE_SSE2__ #pragma GCC pop_options #endif /* __DISABLE_SSE2__ */ around std::float16_t/std::bfloat16_t stuff. Definitely not stage4 material I'm afraid.
next prev parent reply other threads:[~2023-04-14 8:01 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-13 18:58 [Bug c/109504] New: " vd.kraats at hccnet dot nl 2023-04-13 21:30 ` [Bug target/109504] " pinskia at gcc dot gnu.org 2023-04-14 6:32 ` crazylht at gmail dot com 2023-04-14 7:32 ` crazylht at gmail dot com 2023-04-14 7:38 ` [Bug target/109504] [12/13 Regression] " rguenth at gcc dot gnu.org 2023-04-14 8:01 ` jakub at gcc dot gnu.org [this message] 2023-04-14 8:17 ` jakub at gcc dot gnu.org 2023-04-17 6:37 ` crazylht at gmail dot com 2023-04-18 6:39 ` [Bug target/109504] [12/13/14 " crazylht at gmail dot com 2023-05-08 12:26 ` rguenth at gcc dot gnu.org 2023-07-19 1:36 ` cvs-commit at gcc dot gnu.org 2023-07-19 6:48 ` crazylht at gmail dot com 2023-11-30 10:52 ` liuhongt 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-109504-4-v0y3HSN0Qs@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).