- Oct 09, 2012
-
-
Bill Wendling authored
opaque layer is responsible for knowing where that specific attribute is stored. llvm-svn: 165489
-
Argyrios Kyrtzidis authored
ASTContext so that it can be widely available. llvm-svn: 165473
-
Argyrios Kyrtzidis authored
canonical method; avoid storing them again for an out-of-line definition. llvm-svn: 165472
-
Eli Friedman authored
Make sure we allow "#pragma options align=mac68k" in function-local contexts. <rdar://problem/12453134> llvm-svn: 165462
-
Argyrios Kyrtzidis authored
of the initializer is valid before using it. Fixes rdar://12455002&12449015 where local variables of objc objects in ARC mode were not annotated because of the ImplicitValueInitExpr initializer having invalid source range, resulting in the SourceRange of the VarDecl having invalid end location. llvm-svn: 165456
-
- Oct 08, 2012
-
-
Chandler Carruth authored
With this patch Bitrig can use a different c++ library without pain and within the normal commandline parameters. Original patch by David Hill, with lots of fixes and cleanup by me. llvm-svn: 165430
-
Benjamin Kramer authored
PR14040. llvm-svn: 165415
-
Daniel Jasper authored
llvm-svn: 165414
-
Daniel Jasper authored
llvm-svn: 165412
-
Micah Villmow authored
llvm-svn: 165395
-
Daniel Jasper authored
Review: http://llvm-reviews.chandlerc.com/D30 llvm-svn: 165392
-
David Blaikie authored
llvm-svn: 165384
-
David Blaikie authored
llvm-svn: 165383
-
- Oct 07, 2012
-
-
Rafael Espindola authored
llvm-svn: 165370
-
Rafael Espindola authored
The darwin change should be a nop since Triple::getArchTypeForDarwinArchName doesn't know about amd64. If things like amd64-mingw32 are to be rejected, we should print a error earlier on instead of silently using the wrong abi. Remove old comment that looks out of place, this is "in clang". llvm-svn: 165368
-
- Oct 06, 2012
-
-
Benjamin Kramer authored
GCC has always supported this on PowerPC and 4.8 supports it on all platforms, so it's a good idea to expose it in clang too. LLVM supports this on all targets. llvm-svn: 165362
-
Jordan Rose authored
The Clang ASTs are a DAG, not a pure tree. However, ParentMap has to choose a single parent for each object. In the main (only?) cases in which the AST forms a DAG, it protects from multiple traversal by using OpaqueValueExprs. Previously, ParentMap would just unconditionally look through all OpaqueValueExprs when building its map. In order to make this behavior better for the analyzer's diagnostics, ParentMap was changed to not set a statement's parent if there already was one in the map. However, ParentMap is supposed to allow updating existing mappings by calling addStmt once again. This change makes the "transparency" of OpaqueValueExprs explicit, and disables it when it is not desired, rather than checking the current contents of the map. This new code seems like a big change, but it should actually have essentially the same performance as before. Only OpaqueValueExprs and their users (PseudoObjectExpr and BinaryConditionalOperator) will have any different behavior. There should be no user-visible functionality change, though a test has been added for the current behavior of BinaryConditionalOperator source locations and accompanying Xcode arrows (which are not so great...). llvm-svn: 165355
-
Jordan Rose authored
Some implicit statements, such as the implicit 'self' inserted for "free" Objective-C ivar access, have invalid source locations. If one of these statements is the location where an issue is reported, we'll now look at the enclosing statements for a valid source location. <rdar://problem/12446776> llvm-svn: 165354
-
Alex Rosenberg authored
llvm-svn: 165343
-
DeLesley Hutchins authored
llvm-svn: 165339
-
- Oct 05, 2012
-
-
Michael Liao authored
llvm-svn: 165325
-
Abramo Bagnara authored
llvm-svn: 165298
-
Eli Friedman authored
PR14029, clang part. llvm-svn: 165289
-
Richard Smith authored
Workaround for libstdc++4.6 <atomic> bug: make comment more explicit about what's going on, per Sean Silva's suggestion. llvm-svn: 165286
-
David Blaikie authored
This appears to be consistent with GCC's implementation of the same warning under -Wparentheses. Suppressing a << b + c for cases where 'a' is a user defined type for compatibility with C++ stream IO. Otherwise suggest parentheses around the addition or subtraction subexpression. (this came up when MSVC was complaining (incorrectly, so far as I can tell) about a perceived violation of this within the LLVM codebase, PR14001) llvm-svn: 165283
-
Argyrios Kyrtzidis authored
that are associated with a (sub)module. llvm-svn: 165279
-
Argyrios Kyrtzidis authored
loaded entities vector, otherwise its meaning will change when a module is imported and the vector size changes. llvm-svn: 165278
-
Argyrios Kyrtzidis authored
import declaration. llvm-svn: 165277
-
Richard Smith authored
- outside C++, return undef (behavior is not undefined unless the value is used) - in C++, with -fcatch-undefined-behavior, perform an appropriate trap - in C++, produce an 'unreachable' (behavior is undefined immediately) llvm-svn: 165273
-
Richard Smith authored
a non-inline namespace, then reopens it as inline to try to add its symbols to the surrounding namespace. In this one special case, permit the namespace to be reopened as inline, and patch up the name lookup tables to match. llvm-svn: 165263
-
- Oct 04, 2012
-
-
Abramo Bagnara authored
llvm-svn: 165259
-
Abramo Bagnara authored
llvm-svn: 165258
-
Abramo Bagnara authored
llvm-svn: 165256
-
Benjamin Kramer authored
crtfastmath.o contains routines to set the floating point flags to a faster, unsafe mode. Linking it in speeds up code dealing with denormals significantly (PR14024). For now this is only enabled on linux where I can test it and crtfastmath.o is widely available. We may want to provide a similar file with compiler-rt eventually and/or enable it on other platforms too. llvm-svn: 165240
-
Michael Han authored
For GNU attributes, instead of reusing attribute source location for the scope location, use SourceLocation() since GNU attributes don not have scope tokens. llvm-svn: 165234
-
Benjamin Kramer authored
This may be slightly more efficient and is definitely more readable. llvm-svn: 165217
-
Logan Chien authored
llvm-svn: 165216
-
Axel Naumann authored
Fix r165005: The lexical DeclContext is not the right place to make a decision about whether we need to call tryAddTopLevelDecl or not. That call should be made when the DeclContext's redeclaration context is the translation unit. llvm-svn: 165215
-
Nick Lewycky authored
llvm-svn: 165202
-
Lang Hames authored
up being contracted during codegen. llvm-svn: 165197
-