[Bug c++/100616] [modules] ICE when a variable of class taking a non-type template argument is defined both inside and outside the module

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100616 Patrick Palka changed: What|Removed |Added CC||johelegp at gmail dot com --- Comment

[Bug c++/100616] [modules] ICE when a variable of class taking a non-type template argument is defined both inside and outside the module

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100616 Patrick Palka changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---

[Bug c++/100616] [modules] ICE when a variable of class taking a non-type template argument is defined both inside and outside the module

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100616 --- Comment #3 from CVS Commits --- The master branch has been updated by Nathan Sidwell : https://gcc.gnu.org/g:a1f7f9541c2b20eb44750b9c15cd831c62d67f21 commit r13-2953-ga1f7f9541c2b20eb44750b9c15cd831c62d67f21 Author: Nathan Sidwell Date:

[Bug c++/100616] [modules] ICE when a variable of class taking a non-type template argument is defined both inside and outside the module

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100616 --- Comment #2 from wang ivor --- 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

[Bug c++/100616] [modules] ICE when a variable of class taking a non-type template argument is defined both inside and outside the module

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100616 --- Comment #1 from wang ivor --- Seems like the same bug happens whenever you use a class template with a non-type template argument in two modules with dependency. This seems to be a pretty serious bug that renders non-type template argument