| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | [Modules TS] Diagnose attempts to enter module implementation units without ↵ | Richard Smith | 2017-10-10 | 1 | -1/+4 |
| | | | | | | | the module interface being available. llvm-svn: 315381 | ||||
| * | [modules-ts] Omit submodule semantics for TS modules | Boris Kolpackov | 2017-08-29 | 1 | -2/+7 |
| | | | | | | | | | | | | | If a TS module name has more than one component (e.g., foo.bar) then we erroneously activated the submodule semantics when encountering a module declaration in the module implementation unit (e.g., 'module foo.bar;'). Reviewed By: rsmith Differential Revision: https://reviews.llvm.org/D35678 llvm-svn: 312007 | ||||
| * | [modules ts] Declarations from a module interface unit are only visible outside | Richard Smith | 2017-07-05 | 1 | -2/+2 |
| | | | | | | | the module if declared in an export block. llvm-svn: 307115 | ||||
| * | Rearrange some Modules TS testcases into test/CXX/modules-ts. | Richard Smith | 2017-04-22 | 1 | -0/+41 |
| llvm-svn: 301066 | |||||
 |
index : bcm5719-llvm | |
| Project Ortega BCM5719 LLVM | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|