public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/108030] `std::experimental::simd` not inlined Date: Fri, 24 Feb 2023 18:40:52 +0000 [thread overview] Message-ID: <bug-108030-4-sQpV21ctUB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108030-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108030 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Matthias Kretz <mkretz@gcc.gnu.org>: https://gcc.gnu.org/g:e37b04328ae68f91efe1fb2c5de9122be34bc74a commit r13-6334-ge37b04328ae68f91efe1fb2c5de9122be34bc74a Author: Matthias Kretz <m.kretz@gsi.de> Date: Mon Feb 20 17:49:37 2023 +0100 libstdc++: Always-inline most of non-cmath fixed_size implementation For simd, the inlining behavior should be similar to builtin types. (No operator on buitin types is ever translated into a function call.) Therefore, always_inline is the right choice (i.e. inline on -O0 as well). Signed-off-by: Matthias Kretz <m.kretz@gsi.de> libstdc++-v3/ChangeLog: PR libstdc++/108030 * include/experimental/bits/simd_fixed_size.h (_SimdImplFixedSize::_S_broadcast): Replace inline with _GLIBCXX_SIMD_INTRINSIC. (_SimdImplFixedSize::_S_generate): Likewise. (_SimdImplFixedSize::_S_load): Likewise. (_SimdImplFixedSize::_S_masked_load): Likewise. (_SimdImplFixedSize::_S_store): Likewise. (_SimdImplFixedSize::_S_masked_store): Likewise. (_SimdImplFixedSize::_S_min): Likewise. (_SimdImplFixedSize::_S_max): Likewise. (_SimdImplFixedSize::_S_complement): Likewise. (_SimdImplFixedSize::_S_unary_minus): Likewise. (_SimdImplFixedSize::_S_plus): Likewise. (_SimdImplFixedSize::_S_minus): Likewise. (_SimdImplFixedSize::_S_multiplies): Likewise. (_SimdImplFixedSize::_S_divides): Likewise. (_SimdImplFixedSize::_S_modulus): Likewise. (_SimdImplFixedSize::_S_bit_and): Likewise. (_SimdImplFixedSize::_S_bit_or): Likewise. (_SimdImplFixedSize::_S_bit_xor): Likewise. (_SimdImplFixedSize::_S_bit_shift_left): Likewise. (_SimdImplFixedSize::_S_bit_shift_right): Likewise. (_SimdImplFixedSize::_S_remquo): Add inline keyword (to be explicit about not always-inline, yet). (_SimdImplFixedSize::_S_isinf): Likewise. (_SimdImplFixedSize::_S_isfinite): Likewise. (_SimdImplFixedSize::_S_isnan): Likewise. (_SimdImplFixedSize::_S_isnormal): Likewise. (_SimdImplFixedSize::_S_signbit): Likewise.
next prev parent reply other threads:[~2023-02-24 18:40 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-09 11:29 [Bug libstdc++/108030] New: " bernhardmgruber at gmail dot com 2022-12-09 12:15 ` [Bug libstdc++/108030] " mkretz at gcc dot gnu.org 2022-12-09 12:15 ` mkretz at gcc dot gnu.org 2022-12-09 14:13 ` jakub at gcc dot gnu.org 2022-12-09 14:51 ` mkretz at gcc dot gnu.org 2022-12-09 14:55 ` jakub at gcc dot gnu.org 2023-02-16 14:58 ` cvs-commit at gcc dot gnu.org 2023-02-19 14:39 ` mkretz at gcc dot gnu.org 2023-02-19 15:21 ` bernhardmgruber at gmail dot com 2023-02-23 14:03 ` cvs-commit at gcc dot gnu.org 2023-02-23 14:04 ` cvs-commit at gcc dot gnu.org 2023-02-23 16:31 ` cvs-commit at gcc dot gnu.org 2023-02-23 19:46 ` cvs-commit at gcc dot gnu.org 2023-02-24 18:40 ` cvs-commit at gcc dot gnu.org [this message] 2023-02-24 18:54 ` mkretz at gcc dot gnu.org 2023-04-26 6:57 ` rguenth at gcc dot gnu.org 2023-04-30 9:06 ` mkretz at gcc dot gnu.org 2023-05-23 10:02 ` cvs-commit at gcc dot gnu.org 2023-05-23 10:02 ` cvs-commit at gcc dot gnu.org 2023-05-23 10:02 ` cvs-commit at gcc dot gnu.org 2023-05-25 7:04 ` cvs-commit at gcc dot gnu.org 2023-05-25 7:04 ` cvs-commit at gcc dot gnu.org 2023-05-25 7:04 ` cvs-commit at gcc dot gnu.org 2023-05-25 7:08 ` mkretz 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-108030-4-sQpV21ctUB@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).