public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/114803] simd conversion to [[gnu::vector_size(N)]] type hits invalid code in experimental/bits/simd_builtin.h Date: Thu, 06 Jun 2024 07:50:13 +0000 [thread overview] Message-ID: <bug-114803-4-JJJekiQRZx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114803-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114803 --- Comment #16 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- That macro is used within libstdc++ to avoid relying on C99 functions when the target C library is not C99-compliant. It involves leaving out C++ standard bits that would depend on functions that the C library doesn't offer, including some of the <cmath> declarations in ::std::. IMHO it would make sense to omit simd functions corresponding to C99/TR1 ones known to be missing. Now, it's unclear to me whether we'd be better off omitting the entire set of C99/TR1 math functions as a block, or whether there'd be any benefit from considering individual functions separately. newlib, for example, exports a number of the C99/TR1 functions, but not all of them, so the macro is not defined.
prev parent reply other threads:[~2024-06-06 7:50 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-22 12:56 [Bug libstdc++/114803] New: " mkretz at gcc dot gnu.org 2024-04-22 12:58 ` [Bug libstdc++/114803] " mkretz at gcc dot gnu.org 2024-04-22 18:56 ` cvs-commit at gcc dot gnu.org 2024-04-22 18:58 ` mkretz at gcc dot gnu.org 2024-05-07 16:19 ` cvs-commit at gcc dot gnu.org 2024-05-08 16:15 ` cvs-commit at gcc dot gnu.org 2024-05-10 14:07 ` cvs-commit at gcc dot gnu.org 2024-05-10 14:24 ` mkretz at gcc dot gnu.org 2024-05-30 8:14 ` aoliva at gcc dot gnu.org 2024-05-30 12:04 ` aoliva at gcc dot gnu.org 2024-05-31 8:47 ` mkretz at gcc dot gnu.org 2024-05-31 10:59 ` aoliva at gcc dot gnu.org 2024-05-31 11:45 ` aoliva at gcc dot gnu.org 2024-05-31 13:42 ` mkretz at gcc dot gnu.org 2024-05-31 14:18 ` mkretz at gcc dot gnu.org 2024-05-31 17:16 ` aoliva at gcc dot gnu.org 2024-06-02 15:05 ` mkretz at gcc dot gnu.org 2024-06-06 7:50 ` aoliva at gcc dot gnu.org [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=bug-114803-4-JJJekiQRZx@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).