| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
| |
was probably meant to be 'typename', which we will have already suggested if it
is appropriate.
llvm-svn: 145395
|
| |
|
|
|
|
|
|
| |
definitions tokens
for late parsing.
llvm-svn: 145394
|
| |
|
|
| |
llvm-svn: 145393
|
| |
|
|
|
|
|
|
|
|
|
|
| |
the driver.
clang/lib/Driver/Driver.cpp: Don't pass through negative exit status, or parent would be confused.
llvm::sys::Program::Wait(): Suppose 0x8000XXXX and 0xC000XXXX as abnormal exit code and pass it as negative value.
Win32 Exception Handler: Exit with ExceptionCode on an unhandle exception.
llvm-svn: 145389
|
| |
|
|
| |
llvm-svn: 145377
|
| |
|
|
|
|
|
|
| |
declaration at namespace scope is followed by a semicolon and an open-brace
(or in C++, a 'try', ':' or '='), then the error is probably a function
definition with a spurious ';', rather than a mysterious '{'.
llvm-svn: 145372
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
expansions/definition
of a macro in a file).
As a bonus, also make searching for declarations more efficient by ignoring
preprocessing entities when we know that we are looking for a declaration.
Fixes rdar://10427411.
llvm-svn: 145369
|
| |
|
|
| |
llvm-svn: 145360
|
| |
|
|
| |
llvm-svn: 145359
|
| |
|
|
|
|
| |
// rdar://10453342
llvm-svn: 145358
|
| |
|
|
|
|
| |
<rdar://problem/10473903>.
llvm-svn: 145339
|
| |
|
|
|
|
| |
formatting here a bit... mostly to my preferred bikeshed-blue.
llvm-svn: 145337
|
| |
|
|
|
|
|
|
|
|
|
| |
the release notes despite their awesomeness. If we had a thorough
discussion of the performance of Clang in 2.9 vs. 3.0, the first would
be more relevant, but we don't. The serialization stuff hopefully isn't
terribly visible to end users.
Objections to these omissions are of course welcome. =]
llvm-svn: 145336
|
| |
|
|
|
|
|
| |
extensions and one infrastructure feature addition that has a direct
impact on other projects which use Clang.
llvm-svn: 145335
|
| |
|
|
| |
llvm-svn: 145334
|
| |
|
|
|
|
| |
from the Objective-C experts, but the basic stuff is there now.
llvm-svn: 145333
|
| |
|
|
|
|
|
|
| |
attribute. This prevents the stack slot allocator from coming along and using a
stack which it thinks is available but isn't.
<rdar://problem/10492556>
llvm-svn: 145332
|
| |
|
|
|
|
|
|
| |
Ruben Van Boxem.
(We should probably start doing some sort of autodetection like we do on Linux at some point.)
llvm-svn: 145326
|
| |
|
|
| |
llvm-svn: 145325
|
| |
|
|
|
|
| |
PR11444/PR11445.
llvm-svn: 145321
|
| |
|
|
|
|
| |
I think that's enough for my release notes.
llvm-svn: 145320
|
| |
|
|
| |
llvm-svn: 145317
|
| |
|
|
| |
llvm-svn: 145315
|
| |
|
|
|
|
|
|
| |
when they are greater than 128 bits. This was incorrectly coercing things like long3 into a double2.
Add test case.
llvm-svn: 145312
|
| |
|
|
| |
llvm-svn: 145311
|
| |
|
|
|
|
|
|
| |
return the module itself (in the module map) rather than returning the
umbrella header used to build the module. While doing this, make sure
that we're inferring modules for frameworks to build that module.
llvm-svn: 145310
|
| |
|
|
|
|
|
|
| |
accurate than my original notes were based on IRC conversations. Windows
folks, please edit as needed to make this closer to the truth if I've
still got it wrong.
llvm-svn: 145309
|
| |
|
|
| |
llvm-svn: 145308
|
| |
|
|
|
|
|
| |
add a bit to that section about the many bug-finding warnings that Clang
has grown since 2.9 as this is one of the more visible new additions.
llvm-svn: 145307
|
| |
|
|
|
|
| |
enough to merit space in the release notes.
llvm-svn: 145306
|
| |
|
|
| |
llvm-svn: 145305
|
| |
|
|
|
|
| |
feels a bit spartan currently.
llvm-svn: 145302
|
| |
|
|
|
|
|
|
|
| |
before passing to RangeCompare.
Though no idea how this can occur with the decls returned from
findFileRegionDecls().
llvm-svn: 145301
|
| |
|
|
| |
llvm-svn: 145299
|
| |
|
|
| |
llvm-svn: 145298
|
| |
|
|
| |
llvm-svn: 145297
|
| |
|
|
| |
llvm-svn: 145293
|
| |
|
|
|
|
|
|
|
| |
stub for OpenCL work. I can't really dig enough out of the commit log
messages other than to tell that a lot of work went into this in the 2.9
-> 3.0 timeframe. I'll let the folks touching it decide if it merits
a spot in the release notes and provide the appropriate details if so.
llvm-svn: 145291
|
| |
|
|
| |
llvm-svn: 145290
|
| |
|
|
|
|
|
|
| |
easier. Move the CUDA bits and the C1X/C++11 atomics stuff there. We
haven't exposed a __has_feature for the atomic builtins, so none of this
is available yet...
llvm-svn: 145288
|
| |
|
|
|
|
| |
this stage.
llvm-svn: 145286
|
| |
|
|
|
|
| |
more love w.r.t. platforms other than Linux?
llvm-svn: 145285
|
| |
|
|
|
|
| |
C++11 standard.
llvm-svn: 145284
|
| |
|
|
| |
llvm-svn: 145283
|
| |
|
|
|
|
|
|
|
|
|
| |
The performance improvement was committed after the 3.0 branch.
Constructors/destructors are handled by the CFG, but we do not do anything
special for them in the analyzer yet.
Since we do not have an open source release qualification for the analyzer,
we are not investing into creating the proper release notes for it.
llvm-svn: 145281
|
| |
|
|
|
|
| |
__has_feature(address_sanitizer)
llvm-svn: 145276
|
| |
|
|
| |
llvm-svn: 145275
|
| |
|
|
| |
llvm-svn: 145274
|
| |
|
|
| |
llvm-svn: 145271
|
| |
|
|
|
|
|
|
| |
when computing the exception specification of a copy or move constructor,
ignore non-static data member initializers. Fixes PR11418 /
<rdar://problem/10478642>.
llvm-svn: 145269
|