Skip to content

Conversation

@Teemperor
Copy link
Contributor

With C++ modules we are supposed to have a unique module name where
each module contains different headers. But smatrix(32) or genvector(32)
currently have the same contents and also the same name. As we
anyway also have a combined LinkDef file for both cases, we just
unify those two dictionaries when using runtime_modules and have
only a single module in the end which has an unique name and
unique contents.

@phsft-bot
Copy link

Starting build on centos7/gcc49, mac1012/native, slc6/gcc49, slc6/gcc62, ubuntu14/native with flags -Dvc=OFF -Dimt=ON -Dccache=ON
How to customize builds

@Teemperor Teemperor changed the title [cxxmodules] Unified *32 dictionaries into one [cxxmodules] Unify *32 dictionaries into one Sep 4, 2017
@phsft-bot
Copy link

Starting build on centos7/gcc49, mac1012/native, slc6/gcc49, slc6/gcc62, ubuntu14/native with flags -Dvc=OFF -Dimt=ON -Dccache=ON
How to customize builds

@Teemperor
Copy link
Contributor Author

@phsft-bot build

@phsft-bot
Copy link

Starting build on centos7/gcc49, mac1012/native, slc6/gcc49, slc6/gcc62, ubuntu14/native with flags -Dvc=OFF -Dimt=ON -Dccache=ON
How to customize builds

With C++ modules we are supposed to have a unique module name where
each module contains different headers. But smatrix(32) or genvector(32)
currently have the same contents and also the same name. As we
anyway also have a combined LinkDef file for both cases, we just
unify those two dictionaries when using runtime_modules and have
only a single module in the end which has an unique name and
unique contents.
@Teemperor Teemperor closed this Sep 4, 2017
@pcanal
Copy link
Member

pcanal commented Sep 5, 2017

(As it seems you discovered :)), the source file of those dictionaries must be distinct as one of the mechanism used for bootstrapping is function overload resolution based on the requested types. However since TemplateName and TemplateName<Double32_t> are, for the C++ compiler, the same name we end with both a compilation error and if the compile succeeds then a call to the 'wrong' function and/or a missing call to one of the two (similar) overloads.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants