public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nikolasklauser at berlin dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110000] New: GCC should implement exclude_from_explicit_instantiation Date: Fri, 26 May 2023 20:25:48 +0000 [thread overview] Message-ID: <bug-110000-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110000 Bug ID: 110000 Summary: GCC should implement exclude_from_explicit_instantiation Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nikolasklauser at berlin dot de Target Milestone: --- `exclude_from_explicit_instantiation` is an attribute implemented by clang. It tells the compiler that a function should not be part of an explicit instantiation. This allows libraries to have greater control over which functions are part of their ABI and which aren't. It is used extensively in libc++ to keep the ABI surface as small as possible. Currently, libc++ uses always_inline if exclude_from_explicit_instantiation isn't available, resulting in almost every function in the library being declared as always_inline. Replacing always_inline with exclude_from_explicit_instantiation would approximately halve the time it takes to run the libc++ test suite with GCC. (removing always_inline brings the time down to about the same as clang takes)
next reply other threads:[~2023-05-26 20:25 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-26 20:25 nikolasklauser at berlin dot de [this message] 2023-05-26 20:31 ` [Bug c++/110000] " ldionne.2 at gmail dot com 2023-05-26 20:33 ` pinskia at gcc dot gnu.org 2023-05-26 20:35 ` pinskia at gcc dot gnu.org 2023-05-26 20:42 ` nikolasklauser at berlin dot de 2023-05-27 10:39 ` fw at gcc dot gnu.org 2023-05-27 23:40 ` nikolasklauser at berlin dot de 2023-05-28 6:13 ` fw at gcc dot gnu.org 2023-05-28 14:31 ` nikolasklauser at berlin dot de 2023-05-31 15:40 ` ldionne.2 at gmail dot com 2023-05-31 16:48 ` redi at gcc dot gnu.org 2023-05-31 16:52 ` redi at gcc dot gnu.org 2023-05-31 17:33 ` nikolasklauser at berlin dot de 2023-06-01 18:00 ` ldionne.2 at gmail dot com
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-110000-4@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).