This is an archive of the discontinued LLVM Phabricator instance.

[libc++] Disable local submodule visibility in the modules build
ClosedPublic

Authored by ldionne on Feb 10 2022, 12:07 PM.

Details

Reviewers
None
Group Reviewers
Restricted Project
Commits
rG73382278825d: [libc++] Disable local submodule visibility in the modules build

Diff Detail

Event Timeline

ldionne created this revision.Feb 10 2022, 12:07 PM
ldionne requested review of this revision.Feb 10 2022, 12:07 PM
Herald added a project: Restricted Project. · View Herald TranscriptFeb 10 2022, 12:07 PM
Herald added a reviewer: Restricted Project. · View Herald Transcript

This was discussed in https://reviews.llvm.org/D119036. I suspect this won't pass, but I want to see what CI will say.

ldionne updated this revision to Diff 407934.Feb 11 2022, 10:10 AM

Try to remove textual for config and config_site, which is what's causing problems with LLDB.

aprantl added inline comments.Feb 11 2022, 12:26 PM
libcxx/utils/libcxx/test/params.py
74

I don't really understand the libcxx test configuration, but it looks like this changes the test that the std module can be built to not use LSV. Should we maybe test both LSV and non-LSV configs going forward?

ldionne added inline comments.Feb 11 2022, 12:52 PM
libcxx/utils/libcxx/test/params.py
74

Honestly, I'd rather just test the default -fmodules flag, that's it. I don't even know why we had LSV turned on previously. I have no desire to start supporting various ways to build with modules, just whatever the default modules build is. We don't really have that much CI hardware to spare.

I'm going to ship this since it looks like CI is happy with it.

ldionne accepted this revision as: Restricted Project.Feb 11 2022, 12:52 PM
This revision was not accepted when it landed; it landed in state Needs Review.Feb 11 2022, 12:53 PM
This revision was landed with ongoing or failed builds.
This revision was automatically updated to reflect the committed changes.