On 11/12/20 9:24 AM, Nathan Sidwell wrote:
> On 11/3/20 4:17 PM, Nathan Sidwell wrote:
>> this is the module mapper client and server pieces. It features a
>> default resolver that can read a text file, or generate default
>> mappings from module name to cmi name.
>
> Richard rightly suggested
Nathan Sidwell writes:
> These are needed as they also serve to inform the mapper of a dependency
> edge.
Ok, that makes sense (and thanks for making it optional via a flag).
One thing that is still missing in this area is the dependency on
stdc-predef.h. In other words, we now can get everyth
On 11/3/20 4:17 PM, Nathan Sidwell wrote:
this is the module mapper client and server pieces. It features a
default resolver that can read a text file, or generate default mappings
from module name to cmi name.
Richard rightly suggested on IRC that the sample server for the module
mapper sho
On 11/9/20 1:42 AM, Boris Kolpackov wrote:
I've noticed the following issues with the module mapper in the
-fdirectives-only mode:
1. When partially preprocessing the module interface unit, the mapper
receives the MODULE-EXPORT request that's unnecessary (BMI is not
written):
g++ .
I've noticed the following issues with the module mapper in the
-fdirectives-only mode:
1. When partially preprocessing the module interface unit, the mapper
receives the MODULE-EXPORT request that's unnecessary (BMI is not
written):
g++ ... -x c++ -E -fdirectives-only -o hello.gcm.ii h
