Author: borisk
Date: Tue Aug 29 08:30:18 2017
New Revision: 312007
URL: http://llvm.org/viewvc/llvm-project?rev=312007&view=rev
Log:
[modules-ts] Omit submodule semantics for TS modules
If a TS module name has more than one component (e.g., foo.bar) then we
erroneously activated the submodule sem
Author: borisk
Date: Wed Aug 30 01:45:59 2017
New Revision: 312105
URL: http://llvm.org/viewvc/llvm-project?rev=312105&view=rev
Log:
[modules] Add ability to specify module name to module file mapping
Extend the -fmodule-file option to support the [=] value format.
If the name is omitted, then th
Author: borisk
Date: Wed Aug 30 02:15:53 2017
New Revision: 312106
URL: http://llvm.org/viewvc/llvm-project?rev=312106&view=rev
Log:
[docs] Regenerate command line options reference
Modified:
cfe/trunk/docs/ClangCommandLineReference.rst
Modified: cfe/trunk/docs/ClangCommandLineReference.rst
Victor Leschuk writes:
> Hello Boris, looks like this revision broke tests on our win10 builder:
> http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-scei-ps4-windows10pro-fast/builds/11760
>
> Clang :: CXX/modules-ts/basic/basic.link/module-declaration.cpp
>
> I had to revert this revisio
Author: borisk
Date: Wed Aug 30 23:18:08 2017
New Revision: 312217
URL: http://llvm.org/viewvc/llvm-project?rev=312217&view=rev
Log:
Fix path regex in test to match on Windows
Modified:
cfe/trunk/test/CXX/modules-ts/basic/basic.link/module-declaration.cpp
Modified: cfe/trunk/test/CXX/modules
Author: borisk
Date: Wed Aug 30 23:26:43 2017
New Revision: 312220
URL: http://llvm.org/viewvc/llvm-project?rev=312220&view=rev
Log:
[modules] Add ability to specify module name to module file mapping (reapply)
Extend the -fmodule-file option to support the [=] value format.
If the name is omitte
boris-kolpackov wrote:
>clang++ -std=c++20 foo.cpp -c -fmodule-file=X=some/dir/X.pcm
Hm, according to https://clang.llvm.org/docs/StandardCPlusPlusModules.html this
can already be achieved with the `-fmodule-output` options (which I was about
to try in `build2`). Is there a reason a diffe
boris-kolpackov wrote:
If I understand correctly, this invents a new option just to print the std
modules path. Is there a reason why we cannot just print this information as
part of `-print-search-dirs`? The benefit of this will be saving an extra
compiler invocation in case the build system
boris-kolpackov wrote:
> I had looked at `-print-search-dirs` but it seems buggy. For example, it
> ignores the `-stdlib` flag to the compiler invocation.
True. I couldn't find a bug report for this so I filed one:
https://github.com/llvm/llvm-project/issues/76614
> Solving this seems a lot
boris-kolpackov wrote:
I don't know, I feel like you are just kicking the can down the road: if the
user sees a harmless warning continuously, they will suppress this warning, and
then won't see the harmful ones in the future. But then again we do this all
the time in C++, so I guess it's par
boris-kolpackov wrote:
> Maybe then we could adapt the Fortran/ASM convention where an uppercase
> extension means "I need preprocessing" and lowercase doesn't. (tongue lightly
> in cheekā¦)
>From https://build2.org/build2/doc/build2-build-system-manual.xhtml :
> The `preprocessed` property in
11 matches
Mail list logo