| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128385
|
| |
|
|
|
|
| |
CharUnits. No change in functionality intended.
llvm-svn: 128384
|
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128383
|
| |
|
|
|
|
| |
AltiVec vector types. It fixes bug 9347.
llvm-svn: 128381
|
| |
|
|
|
|
|
|
|
|
|
| |
This is basically the same idea as the warning on uninitialized uses of
fields within an initializer list. As such, it is on by default and
under -Wuninitialized.
Original patch by Richard Trieu, with some massaging from me on the
wording and grouping of the diagnostics.
llvm-svn: 128376
|
| |
|
|
|
|
| |
PIM section 2.5.1 - after initialization all elements have the value specified by the literal
llvm-svn: 128375
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Emit them instead with the linkage of the VTT.
I'm actually really ambivalent about this; it's what GCC does, but outside
of improving code size (if the linkage is coalescing), I'm not sure it's
at all relevant. Construction vtables are naturally referenced only by the
VTT, which is itself only referenced by complete-object constructors and
destructors; giving the construction vtables possibly-external linkage is
important if you have an optimization that drills through the VTT to a
reference to a particular construction vtable which it cannot just emit
itself.
llvm-svn: 128374
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These stacks are often less important than those on primary diagnostics.
As the number of notes grows, this becomes increasingly important. The
include stack printing is clever and doesn't print stacks for adjacent
diagnostics from the same file, but when a note is in between a sequence
of errors in a header file, and the notes all refer to some other file,
we end up getting a worst-case ping-pong of include stacks that take up
a great deal of vertical space.
Still, for now, the default behavior isn't changed. We can evaluate user
feedback with the flag.
Patch by Richard Trieu, a couple of style tweaks from me.
llvm-svn: 128371
|
| |
|
|
|
|
|
|
|
| |
default for -fwrapv if that flag isn't specified explicitly. We always
prefer an explict setting of -fwrapv when present. Also adds support for
-fno-wrapv to allow disabling -fwrapv even when -fno-strict-overflow is
passed.
llvm-svn: 128353
|
| |
|
|
|
|
| |
specifications within the global scope, from Elliot Glaysher.
llvm-svn: 128352
|
| |
|
|
|
|
|
|
| |
returned
from an objective-c message: // rdar://9005189
llvm-svn: 128348
|
| |
|
|
|
|
| |
Fixes rdar://9170766.
llvm-svn: 128346
|
| |
|
|
|
|
| |
with '::', when :: isn't the first part of the selector.
llvm-svn: 128344
|
| |
|
|
| |
llvm-svn: 128340
|
| |
|
|
| |
llvm-svn: 128339
|
| |
|
|
| |
llvm-svn: 128337
|
| |
|
|
|
|
|
|
|
| |
platform implies default visibility. To achieve these, refactor our
lookup of explicit visibility so that we search for both an explicit
VisibilityAttr and an appropriate AvailabilityAttr, favoring the
VisibilityAttr if it is present.
llvm-svn: 128336
|
| |
|
|
|
|
| |
editor that doesn't have explicit doxygen support, as per LLVM style guidelines.
llvm-svn: 128335
|
| |
|
|
|
|
|
| |
'unavailable' argument, which specifies that the declaration to which
the attribute appertains is unavailable on that platform.
llvm-svn: 128329
|
| |
|
|
|
|
| |
without a warning.
llvm-svn: 128328
|
| |
|
|
|
|
| |
usually useless, but not always.
llvm-svn: 128326
|
| |
|
|
|
|
|
|
| |
the following '@'. Conceivably, we could skip tokens until something that
can validly start an @interface declaration here, but it's not clear that
it matters.
llvm-svn: 128325
|
| |
|
|
| |
llvm-svn: 128324
|
| |
|
|
|
|
|
| |
FinalOverriders::ComputeBaseOffsets() to CharUnits. No change in
functionality intended.
llvm-svn: 128323
|
| |
|
|
|
|
| |
intended.
llvm-svn: 128321
|
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128318
|
| |
|
|
|
|
| |
functionality intended.
llvm-svn: 128317
|
| |
|
|
|
|
| |
intended.
llvm-svn: 128315
|
| |
|
|
| |
llvm-svn: 128310
|
| |
|
|
|
|
| |
by recent code gen changes. This is tested by global-blocks-lines.exp in gdb testsuite.
llvm-svn: 128303
|
| |
|
|
| |
llvm-svn: 128300
|
| |
|
|
| |
llvm-svn: 128297
|
| |
|
|
| |
llvm-svn: 128292
|
| |
|
|
|
|
| |
Sanity checked by John McCall.
llvm-svn: 128287
|
| |
|
|
| |
llvm-svn: 128281
|
| |
|
|
| |
llvm-svn: 128280
|
| |
|
|
| |
llvm-svn: 128279
|
| |
|
|
|
|
| |
only parse an optional 'final' keyword.
llvm-svn: 128278
|
| |
|
|
|
|
| |
parse it though, although that will change shortly.
llvm-svn: 128277
|
| |
|
|
| |
llvm-svn: 128276
|
| |
|
|
| |
llvm-svn: 128275
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Moved the CGObjCRuntime functions out of CGObjCMac.cpp into CGObjCRuntime.cpp
- Added generic functions in CGObjCRuntime for emitting @try and @synchronize
blocks, usable by any runtime that uses DWARF exceptions.
- Made the GNU runtimes use these functions.
It should now be possible to replace the equivalent functions in
CGObjCNonFragileABIMac with simple calls to these two functions, providing the
runtime functions as arguments. I'll post a diff to the list for review before
making any changes to the Mac runtime stuff.
llvm-svn: 128274
|
| |
|
|
|
|
| |
definitions; they will be allowed in the next C++0x draft.
llvm-svn: 128273
|
| |
|
|
| |
llvm-svn: 128272
|
| |
|
|
|
|
| |
C++0x draft
llvm-svn: 128271
|
| |
|
|
| |
llvm-svn: 128253
|
| |
|
|
| |
llvm-svn: 128251
|
| |
|
|
| |
llvm-svn: 128250
|
| |
|
|
|
|
| |
redeclaration context of each declaration in the identifier chain. Should fix Linux self-host
llvm-svn: 128210
|
| |
|
|
|
|
|
|
|
| |
AttributeLists do not accumulate over the lifetime of parsing, but are
instead reused. Also make the arguments array not require a separate
allocation, and make availability attributes store their stuff in
augmented memory, too.
llvm-svn: 128209
|