Skip to content
Snippets Groups Projects
  1. Sep 17, 2015
  2. Jun 19, 2015
  3. Jun 16, 2015
  4. Mar 26, 2015
  5. Feb 20, 2015
  6. Nov 25, 2014
  7. Oct 24, 2014
  8. Oct 23, 2014
  9. Oct 20, 2014
    • Richard Smith's avatar
      [modules] Add support for #include_next. · ccaf6244
      Richard Smith authored
      #include_next interacts poorly with modules: it depends on where in the list of
      include paths the current file was found. Files covered by module maps are not
      found in include search paths when building the module (and are not found in
      include search paths when @importing the module either), so this isn't really
      meaningful. Instead, we fake up the result that #include_next *should* have
      given: find the first path that would have resulted in the given file being
      picked, and search from there onwards.
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@220177 91177308-0d34-0410-b5e6-96231b3b80d8
      ccaf6244
  10. Oct 01, 2014
    • Richard Smith's avatar
      Enable both C and C++ modules with -fmodules, by switching -fcxx-modules to · ce4ac7ba
      Richard Smith authored
      being on by default. -fno-cxx-modules can still be used to enable C modules but
      not C++ modules, but C++ modules is not significantly less stable than C
      modules any more.
      
      Also remove some of the scare words from the modules documentation. We're
      certainly not going to remove modules support (though we might change the
      interface), and it works well enough to bootstrap and build lots of
      non-trivial code.
      
      Note that this does not represent a commitment to the current interface nor
      implementation, and we still intend to follow whatever direction the C and C++
      committees take regarding modules support.
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@218717 91177308-0d34-0410-b5e6-96231b3b80d8
      ce4ac7ba
  11. Sep 29, 2014
  12. Jul 24, 2014
  13. Apr 23, 2014
  14. Apr 18, 2014
  15. Apr 17, 2014
  16. Mar 28, 2014
  17. Mar 19, 2014
  18. Mar 02, 2014
  19. Mar 01, 2014
    • Richard Smith's avatar
      If a module A exports a macro M, and a module B imports that macro and #undef's · 03f900e7
      Richard Smith authored
      it, importers of B should not see the macro. This is complicated by the fact
      that A's macro could also be visible through a different path. The rules (as
      hashed out on cfe-commits) are included as a documentation update in this
      change.
      
      With this, the number of regressions in libc++'s testsuite when modules are
      enabled drops from 47 to 7. Those remaining 7 are also macro-related, and are
      due to remaining bugs in this change (in particular, the handling of submodules
      is imperfect).
      
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@202560 91177308-0d34-0410-b5e6-96231b3b80d8
      03f900e7
  20. Feb 25, 2014
  21. Oct 28, 2013
  22. Sep 27, 2013
  23. Sep 24, 2013
    • Daniel Jasper's avatar
      Add -fmodule-map-file option. · 1b8840ce
      Daniel Jasper authored
      With this option, arbitrarily named module map files can be specified
      to be loaded as required for headers in the respective (sub)directories.
      
      This, together with the extern module declaration allows for specifying
      module maps in a modular fashion without the need for files called
      "module.map".
      
      Among other things, this allows a directory to contain two modules that
      are completely independent of one another.
      
      Review: http://llvm-reviews.chandlerc.com/D1697.
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@191284 91177308-0d34-0410-b5e6-96231b3b80d8
      1b8840ce
    • Daniel Jasper's avatar
      Module use declarations (II) · ddd2dfc1
      Daniel Jasper authored
      Review: http://llvm-reviews.chandlerc.com/D1546.
      
      I have picked up this patch form Lawrence
      (http://llvm-reviews.chandlerc.com/D1063) and did a few changes.
      
      From the original change description (updated as appropriate):
      This patch adds a check that ensures that modules only use modules they
      have so declared. To this end, it adds a statement on intended module
      use to the module.map grammar:
      
        use module-id
      
      A module can then only use headers from other modules if it 'uses' them.
      This enforcement is off by default, but may be turned on with the new
      option -fmodules-decluse.
      
      When enforcing the module semantics, we also need to consider a source
      file part of a module. This is achieved with a compiler option
      
      -fmodule-name=<module-id>.
      
      The compiler at present only applies restrictions to the module directly
      being built.
      
      git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@191283 91177308-0d34-0410-b5e6-96231b3b80d8
      ddd2dfc1
  24. Sep 11, 2013
  25. Sep 09, 2013
  26. Aug 05, 2013
  27. Jun 20, 2013
  28. Apr 16, 2013
  29. Mar 27, 2013
  30. Mar 25, 2013
  31. Mar 22, 2013
  32. Mar 20, 2013
Loading