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:17:40 +0000 [thread overview] Message-ID: <bug-109504-4-5k5FlmAdvv@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Note, until then we could perhaps do something like: --- gcc/config/i386/avx512fp16intrin.h.jj 2023-01-16 11:52:15.946736083 +0100 +++ gcc/config/i386/avx512fp16intrin.h 2023-04-14 10:13:30.054297659 +0200 @@ -28,6 +28,8 @@ #ifndef __AVX512FP16INTRIN_H_INCLUDED #define __AVX512FP16INTRIN_H_INCLUDED +#ifdef __FLT16_DIG__ + #ifndef __AVX512FP16__ #pragma GCC push_options #pragma GCC target("avx512fp16") @@ -7216,4 +7218,6 @@ _mm512_set1_pch (_Float16 _Complex __A) #pragma GCC pop_options #endif /* __DISABLE_AVX512FP16__ */ +#endif + #endif /* __AVX512FP16INTRIN_H_INCLUDED */ --- gcc/config/i386/avx512fp16vlintrin.h.jj 2023-01-16 11:52:15.946736083 +0100 +++ gcc/config/i386/avx512fp16vlintrin.h 2023-04-14 10:13:54.152946427 +0200 @@ -28,6 +28,8 @@ #ifndef __AVX512FP16VLINTRIN_H_INCLUDED #define __AVX512FP16VLINTRIN_H_INCLUDED +#ifdef __FLT16_DIG__ + #if !defined(__AVX512VL__) || !defined(__AVX512FP16__) #pragma GCC push_options #pragma GCC target("avx512fp16,avx512vl") @@ -3359,4 +3361,6 @@ _mm_set1_pch (_Float16 _Complex __A) #pragma GCC pop_options #endif /* __DISABLE_AVX512FP16VL__ */ +#endif + #endif /* __AVX512FP16VLINTRIN_H_INCLUDED */ --- gcc/config/i386/avxneconvertintrin.h.jj 2023-01-16 11:52:15.949736039 +0100 +++ gcc/config/i386/avxneconvertintrin.h 2023-04-14 10:14:51.280113813 +0200 @@ -48,6 +48,7 @@ _mm256_bcstnebf16_ps (const void *__P) return (__m256) __builtin_ia32_vbcstnebf162ps256 ((const __bf16 *) __P); } +#ifdef __FLT16_DIG__ extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) _mm_bcstnesh_ps (const void *__P) @@ -61,6 +62,7 @@ _mm256_bcstnesh_ps (const void *__P) { return (__m256) __builtin_ia32_vbcstnesh2ps256 ((const _Float16 *) __P); } +#endif extern __inline __m128 __attribute__ ((__gnu_inline__, __always_inline__, __artificial__)) i.e. if _Float16 type isn't usable, just hide all the _Float16 related stuff from the headers. But don't we need the same thing for __bf16 too? There I'm afraid aren't macros for that.
next prev parent reply other threads:[~2023-04-14 8:17 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 2023-04-14 8:17 ` jakub at gcc dot gnu.org [this message] 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-5k5FlmAdvv@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).