| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
For #pragma comment(linker, ...) MSVC expects the comment string to be quoted, but for #pragma comment(lib, ...) the compiler itself quotes the library name.
Since this distinction disappears by the time the directive reaches the backend, move quoting for the "lib" version to the frontend.
Differential Revision: http://reviews.llvm.org/D7653
llvm-svn: 229376
|
| |
|
|
|
|
|
| |
This is nicer in general and gives a better error message, but it also might
bring MSVC 2013 back to life.
llvm-svn: 229374
|
| |
|
|
| |
llvm-svn: 229370
|
| |
|
|
|
|
|
|
| |
subobject initialization is not possible, be sure to note the overall
initialization as having failed so that overload resolution knows that the
relevant candidate is not viable.
llvm-svn: 229353
|
| |
|
|
|
|
| |
__builtin_ia32_pslldqi256 to vector shuffles the backend recognizes. This is a step towards removing the corresponding intrinsics from the backend.
llvm-svn: 229348
|
| |
|
|
|
|
| |
requiring the macro. NFC; Clang edition.
llvm-svn: 229339
|
| |
|
|
| |
llvm-svn: 229338
|
| |
|
|
|
|
| |
macro. NFC; Clang edition.
llvm-svn: 229336
|
| |
|
|
| |
llvm-svn: 229329
|
| |
|
|
| |
llvm-svn: 229327
|
| |
|
|
| |
llvm-svn: 229326
|
| |
|
|
| |
llvm-svn: 229325
|
| |
|
|
| |
llvm-svn: 229295
|
| |
|
|
| |
llvm-svn: 229294
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The first part of that line doesn't parse correctly and ParseClassSpecifier() for
some reason skips to tok::comma to recover, and then
ParseDeclarationSpecifiers() sees the next struct and calls
ParseClassSpecifier() again with the same DeclSpec object.
However, the first call already called ActOnCXXGlobalScopeSpecifier() on the
DeclSpec's CXXScopeSpec, and sema gets confused when this gets called again.
As a fix, let ParseClassSpecifier() (and ParseEnumSpecifier()) call
ParseOptionalCXXScopeSpec() with a temporary CXXScopeSpec object, and only
copy it into the DeclSpec if things work out. (This is also how all the other
functions that set the DeclSpec's TypeSpecScope set it.)
Found by SLi's bot.
llvm-svn: 229293
|
| |
|
|
| |
llvm-svn: 229291
|
| |
|
|
| |
llvm-svn: 229289
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The first part of that line doesn't parse correctly and ParseClassSpecifier() for
some reason skips to tok::comma to recover, and then
ParseDeclarationSpecifiers() sees the next struct and calls
ParseClassSpecifier() again with the same DeclSpec object.
However, the first call already called ActOnCXXGlobalScopeSpecifier() on the
DeclSpec's CXXScopeSpec, and sema gets confused when this gets called again.
As a fix, let ParseClassSpecifier() (and ParseEnumSpecifier()) call
ParseOptionalCXXScopeSpec() with a temporary CXXScopeSpec object, and only
copy it into the DeclSpec if things work out. (This is also how all the other
functions that set the DeclSpec's TypeSpecScope set it.)
Found by SLi's bot.
llvm-svn: 229288
|
| |
|
|
| |
llvm-svn: 229282
|
| |
|
|
|
|
| |
migration
llvm-svn: 229274
|
| |
|
|
|
|
| |
migration
llvm-svn: 229273
|
| |
|
|
|
|
| |
migration
llvm-svn: 229272
|
| |
|
|
|
|
| |
pointer migration
llvm-svn: 229271
|
| |
|
|
| |
llvm-svn: 229270
|
| |
|
|
| |
llvm-svn: 229269
|
| |
|
|
| |
llvm-svn: 229264
|
| |
|
|
|
|
|
|
|
|
| |
We had two bugs:
- We were missing the "on" prefix for unresolved operators.
- We didn't handle the mangling of destructors at all.
This fixes PR22584.
llvm-svn: 229255
|
| |
|
|
| |
llvm-svn: 229242
|
| |
|
|
|
|
|
|
| |
generate weak definitions of the sized operator delete (in terms of unsized operator delete). Instead, provide the funcitonality via a new compiler flag, -fdef-sized-delete.
The current implementation causes link-time ODR violations when the delete symbols are exported into the dynamic table.
llvm-svn: 229241
|
| |
|
|
|
|
| |
accident, and accept them even when they begin '//*'.
llvm-svn: 229240
|
| |
|
|
| |
llvm-svn: 229229
|
| |
|
|
| |
llvm-svn: 229219
|
| |
|
|
|
|
|
| |
they're given a null pointer as an argument, so we do not need to emit null
checks on their results.
llvm-svn: 229213
|
| |
|
|
|
|
|
| |
We could be a little kinder if we did a compare-exchange loop instead of
an atomic-load/store pair.
llvm-svn: 229212
|
| |
|
|
|
|
|
| |
This reverts commit r229123. It was a red herring, the bug was present
without r229082.
llvm-svn: 229205
|
| |
|
|
|
|
|
|
|
| |
Bools are a little tricky, they are i8 in memory and must be coerced
back to i1 before further operations can be performed on them.
This fixes PR22577.
llvm-svn: 229204
|
| |
|
|
|
|
|
|
|
|
|
| |
syntax coming in the near future
The first change won't touch GEPOperators such as these, but the update
script only identifies them by the leading '(' after getelementptr or
'getelementptr inbounds', so update this test to at least have those
features to allow auto-migrating.
llvm-svn: 229198
|
| |
|
|
|
|
| |
change updates
llvm-svn: 229197
|
| |
|
|
|
|
| |
type to getelementptr
llvm-svn: 229196
|
| |
|
|
|
|
| |
a prebuilt form from a module, prefer the modular form, all else being equal.
llvm-svn: 229188
|
| |
|
|
|
|
|
| |
in the middle of emitting an ODR violation diagnostic. I don't yet have a
reduced testcase for this issue, working on it...
llvm-svn: 229167
|
| |
|
|
|
|
| |
visible through multiple imported modules. No functionality change.
llvm-svn: 229147
|
| |
|
|
| |
llvm-svn: 229146
|
| |
|
|
|
|
| |
functionality change.
llvm-svn: 229145
|
| |
|
|
| |
llvm-svn: 229123
|
| |
|
|
| |
llvm-svn: 229093
|
| |
|
|
| |
llvm-svn: 229092
|
| |
|
|
|
|
|
|
|
|
|
|
| |
declarations and just use the legacy namespace qualifier in this file
and the permanent header name.
The old wrapper header is going away to make LLVM's build more modular,
and without updating Clang I can't easily start to add usage of the new
pass manager to Clang. This should make it more clear in the code which
set of types is doing what.
llvm-svn: 229090
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The /volatile:ms semantics turn volatile loads and stores into atomic
acquire and release operations. This distinction is important because
volatile memory operations do not form a happens-before relationship
with non-atomic memory. This means that a volatile store is not
sufficient for implementing a mutex unlock routine.
Differential Revision: http://reviews.llvm.org/D7580
llvm-svn: 229082
|
| |
|
|
|
|
| |
that had optimizations on. This caused the check patterns to not quite match.
llvm-svn: 229073
|