- Jun 26, 2013
-
-
Rafael Espindola authored
llvm-svn: 184922
-
Rafael Espindola authored
llvm-svn: 184921
-
Rafael Espindola authored
llvm-svn: 184920
-
Rafael Espindola authored
llvm-svn: 184919
-
Rafael Espindola authored
llvm-svn: 184918
-
Rafael Espindola authored
llvm-svn: 184917
-
Rafael Espindola authored
llvm-svn: 184916
-
Rafael Espindola authored
llvm-svn: 184915
-
Rafael Espindola authored
I will remove the V1 version as soon as I change clang in the next commit. llvm-svn: 184914
-
Rafael Espindola authored
llvm-svn: 184913
-
Rafael Espindola authored
llvm-svn: 184912
-
Rafael Espindola authored
llvm-svn: 184911
-
Rafael Espindola authored
llvm-svn: 184910
-
Rafael Espindola authored
llvm-svn: 184909
-
Rafael Espindola authored
llvm-svn: 184908
-
Rafael Espindola authored
llvm-svn: 184907
-
Rafael Espindola authored
llvm-svn: 184906
-
Nico Weber authored
llvm-svn: 184905
-
Richard Smith authored
declaration. This PCH a little lazier, and breaks a deserialization cycle that causes crashes with modules enabled. llvm-svn: 184904
-
Faisal Vali authored
As noted by Richard in the post: http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20130624/082605.html, the following code should not add an entry into PendingLocalImplicitInstantiations, since local instantiations should only occur within the context of other instantiations: int foo(double y) { struct Lambda { template<class T> T operator()(T t) const { return t; }; } lambda; return lambda(y); } Hence the attached code does the following: 1) In MarkFunctionReferenced, check if ActiveInstantiations.size() is non-zero before adding to PendingLocalImplicitInstantiations. 2) In InstantiateFunctionDefinition, we swap out/in PendingLocalImplicitInstantiations so that only those pending local instantiations that are added during the instantiation of the current function are instantiated recursively. llvm-svn: 184903
-
Rafael Espindola authored
llvm-svn: 184902
-
Jason Molenda authored
cache ivars/methods. llvm-svn: 184901
-
Enrico Granata authored
Remove the #define USE_CACHE since the formatters cache has been operational for a while now and has not caused issues that warrant disabling it Also, print the cache hits statistics if the log is in debugging mode vs. LLDB being a debug build - this should make it easier to gather useful metrics on cache success rate for real users llvm-svn: 184900
-
rdar://problem/14266578Enrico Granata authored
"command source" was not properly setting the stop-on-error option llvm-svn: 184899
-
rdar://problem/14243761Enrico Granata authored
The argument to -w (--category) in type * list is a regular expression This caused unhappiness with the gnu-libstdc++ category because of the double ++ Now we check for exact textual match as-well-as regexp matching llvm-svn: 184898
-
Nick Lewycky authored
debug statements to add a missing newline. Also canonicalize to '\n' instead of "\n"; the latter calls a function with a loop the former does not. llvm-svn: 184897
-
Nico Weber authored
llvm-svn: 184896
-
Chandler Carruth authored
(thanks!) by deferring the free of the filename until we finish writing the coverage data to that file. Bill, let me know if you'd prefer a different approach! llvm-svn: 184895
-
Nico Weber authored
Before: f(a, b, /*doFoo=*/ false); Now: f(a, b, /*doFoo=*/false); This style is a lot more common: $ ack -H '=\*\/\w' lib | wc -l 1281 $ ack -H '=\*\/ \w' lib | wc -l 70 llvm-svn: 184894
-
rdar://problem/14266411Enrico Granata authored
The semi-unofficial way of returning a status from a Python command was to return a string (e.g. return "no such variable was found") that LLDB would pick as a clue of an error having happened This checkin changes that: - SBCommandReturnObject now exports a SetError() call, which can take an SBError or a plain C-string - script commands now drop any return value and expect the SBCommandReturnObject ("return object") to be filled in appropriately - if you do nothing, a success will be assumed If your commands were relying on returning a value and having LLDB pick that up as an error, please change your commands to SetError() through the return object or expect changes in behavior llvm-svn: 184893
-
Adrian Prantl authored
llvm-svn: 184892
-
Jakob Stoklund Olesen authored
Prefer using RPO.lookup() instead of RPO[] which can mutate the map. llvm-svn: 184891
-
Nick Lewycky authored
answer until after instantiation. Fixes PR16061! llvm-svn: 184890
-
David Majnemer authored
Friend declarations that specify a default argument must be a definition and the only declaration in the translation unit. llvm-svn: 184889
-
Nadav Rotem authored
llvm-svn: 184888
-
Richard Smith authored
llvm-svn: 184887
-
Sean Callanan authored
the target of a typedef when asked for a typedef. llvm-svn: 184886
-
Richard Smith authored
llvm-svn: 184885
-
Richard Smith authored
template parameter. llvm-svn: 184884
-
Matt Beaumont-Gay authored
When the decl that we're getting alignment for is a FieldDecl, and the field's parent record is invalid, skip the actual field alignment calculation (and return 1-byte alignment in the general case). Also, assert in in getASTRecordLayout that the decl is valid. This was inspired by PR16292; see also r184581 and r184751. llvm-svn: 184883
-