public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/105810] __glibcxx_assert can be improved greatly. Date: Wed, 08 Jun 2022 08:57:12 +0000 [thread overview] Message-ID: <bug-105810-4-Y928gEBjgz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105810-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105810 --- Comment #9 from cqwrteur <unlvsur at live dot com> --- if I use std::span<T>, the compiler would have to emit assertions in every function I use them, while the 2nd case would only do that once for the operation [] case for example. It reduces the code size of the function body, allowing more possibility for inlining that particular function for example.
next prev parent reply other threads:[~2022-06-08 8:57 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-01 21:31 [Bug libstdc++/105810] New: " unlvsur at live dot com 2022-06-01 21:34 ` [Bug libstdc++/105810] " unlvsur at live dot com 2022-06-07 13:58 ` redi at gcc dot gnu.org 2022-06-07 23:01 ` unlvsur at live dot com 2022-06-07 23:02 ` unlvsur at live dot com 2022-06-08 8:33 ` redi at gcc dot gnu.org 2022-06-08 8:34 ` unlvsur at live dot com 2022-06-08 8:50 ` redi at gcc dot gnu.org 2022-06-08 8:53 ` unlvsur at live dot com 2022-06-08 8:57 ` unlvsur at live dot com [this message] 2022-06-08 8:58 ` unlvsur at live dot com 2024-02-03 10:58 ` redi 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-105810-4-Y928gEBjgz@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).