public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "connor.baker at tweag dot io" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/30909] aarch64: using intrinsic vector types in math-vector.h breaks C-parsing tools
Date: Thu, 02 Nov 2023 13:41:35 +0000 [thread overview]
Message-ID: <bug-30909-131-cnlutKqzcq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30909-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30909
Connor Baker <connor.baker at tweag dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |connor.baker at tweag dot io
--- Comment #2 from Connor Baker <connor.baker at tweag dot io> ---
Adding some additional context:
We're running into this issue in Nixpkgs:
https://github.com/NixOS/nixpkgs/pull/264599#pullrequestreview-1707381631.
The GLIBC 2.38 update introduces intrinsics for `aarch64-linux` in `math.h`.
NVCC (NVIDIA's CUDA Compiler) declares itself to be the same compiler as its
host compiler. This causes inclusion of unsupported `aarch64-linux` intrinsics.
NVCC is now unable to compile any CUDA file for `aarch64-linux` because it does
not support these intrinsics:
https://forums.developer.nvidia.com/t/nvcc-fails-to-build-with-arm-neon-instructions-cpp-vs-cu/248355/2.
I'll be submitting the same patch I've made for Nixpkgs.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-02 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 11:30 [Bug math/30909] New: " simon.chopin at canonical dot com
2023-09-27 14:28 ` [Bug math/30909] " simon.chopin at canonical dot com
2023-11-02 13:41 ` connor.baker at tweag dot io [this message]
2024-05-06 20:23 ` aurelien at aurel32 dot net
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-30909-131-cnlutKqzcq@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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).