From: Harald Anlauf <anlauf@gmx.de>
To: fortran <fortran@gcc.gnu.org>
Subject: Fw: Today's build of trunk with --disable-bootstrap fails for me...
Date: Mon, 20 Nov 2023 22:25:47 +0100 [thread overview]
Message-ID: <trinity-534f29d5-d144-4857-80a2-49cda6d8ff0a-1700515547833@3c-app-gmx-bs27> (raw)
In-Reply-To: <trinity-47672294-3c8e-4e3c-8622-01a40778811d-1700510484863@3c-app-gmx-bs49>
As I could not find any way to proceed, I submitted my findings
as PR112643 and hope to get feedback.
Harald
> Gesendet: Montag, 20. November 2023 um 21:01 Uhr
> Von: "Harald Anlauf" <anlauf@gmx.de>
> An: "fortran" <fortran@gcc.gnu.org>
> Betreff: Today's build of trunk with --disable-bootstrap fails for me...
>
> Hi,
>
> does anybody else have the same issue?
>
> I usually build trunk with --disable-bootstrap, e.g. 14-trunk using
> gcc-13, and rarely encounter problems. Some change between yesterday
> and today (likely r14-5607-g2f8f7ee2db82a3, Initial support for AVX10.1)
> leads to the following problem:
>
> When building aatree.o, I get:
>
> In file included from /work/gnu/git/build-trunk/gcc/include/immintrin.h:103,
> from /work/gnu/git/build-trunk/gcc/include/x86intrin.h:32,
> from ../../../gcc-trunk/libitm/config/x86/target.h:26,
> from ../../../gcc-trunk/libitm/libitm_i.h:74,
> from ../../../gcc-trunk/libitm/aatree.cc:28:
> /work/gnu/git/build-trunk/gcc/include/avx512vp2intersectvlintrin.h: In function 'void _mm_2intersect_epi32(__m128i, __m128i, __mmask8*, __mmask8*)':
> /work/gnu/git/build-trunk/gcc/include/avx512vp2intersectvlintrin.h:42:3: error: '__builtin_ia32_2intersectd128' was not declared in this scope; did you mean '__builtin_ia32_2intersectd512'?
> 42 | __builtin_ia32_2intersectd128 (__U, __M, (__v4si) __A, (__v4si) __B);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> | __builtin_ia32_2intersectd512
> /work/gnu/git/build-trunk/gcc/include/avx512vp2intersectvlintrin.h: In function 'void _mm256_2intersect_epi32(__m256i, __m256i, __mmask8*, __mmask8*)':
> /work/gnu/git/build-trunk/gcc/include/avx512vp2intersectvlintrin.h:50:3: error: '__builtin_ia32_2intersectd256' was not declared in this scope; did you mean '__builtin_ia32_2intersectd512'?
> 50 | __builtin_ia32_2intersectd256 (__U, __M, (__v8si) __A, (__v8si) __B);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> | __builtin_ia32_2intersectd512
>
> etc.
>
> What am I missing?
>
> Harald
>
prev parent reply other threads:[~2023-11-20 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 20:01 Harald Anlauf
2023-11-20 21:25 ` Harald Anlauf [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=trinity-534f29d5-d144-4857-80a2-49cda6d8ff0a-1700515547833@3c-app-gmx-bs27 \
--to=anlauf@gmx.de \
--cc=fortran@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).