public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amorvincitomnia.iw at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100616] [modules] ICE when a variable of class taking a non-type template argument is defined both inside and outside the module Date: Sun, 16 May 2021 09:22:23 +0000 [thread overview] Message-ID: <bug-100616-4-FqoHB71bxU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100616-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100616 --- Comment #2 from wang ivor <amorvincitomnia.iw at gmail dot com> --- One workaround I found is to always use templates to refer to C inside modules and only ever instantiate them in the outermost translation units. Or, if you only instantiate C with template arguments of primitive types (e.g. int, char, pointer types of primitive types, etc.) this bug doesn't happen.
next prev parent reply other threads:[~2021-05-16 9:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-15 18:59 [Bug c++/100616] New: [modules] ICE when a class template taking a non-type template argument is used both inside and outside the defining module amorvincitomnia.iw at gmail dot com 2021-05-15 20:11 ` [Bug c++/100616] [modules] ICE when a variable of class taking a non-type template argument is defined both inside and outside the module amorvincitomnia.iw at gmail dot com 2021-05-16 9:22 ` amorvincitomnia.iw at gmail dot com [this message] 2022-09-29 11:42 ` cvs-commit at gcc dot gnu.org 2022-09-29 21:05 ` ppalka at gcc dot gnu.org 2022-10-18 15:10 ` ppalka 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-100616-4-FqoHB71bxU@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).