- Aug 13, 2013
-
-
Sean Callanan authored
a bunch of semicolons where the IndirectFieldDecls were. These IndirectFieldDecls should have been implicit. <rdar://problem/14628784> llvm-svn: 188247
-
rdar://problem/14717184Greg Clayton authored
LLDB needs in memory module load level settings to control how much information is read from memory when loading in memory modules. This change adds a new setting: (lldb) settings set target.memory-module-load-level [minimal|partial|complete] minimal will load only sections (no symbols, or function bounds via function starts or EH frame) partial will load sections + bounds complete will load sections + bounds + symbols llvm-svn: 188246
-
David Majnemer authored
Summary: Properly mangle declarations showing up in template arguments that are reference parameters. Fun-fact: undname cannot handle these! Reviewers: rnk, cdavis5x Reviewed By: rnk CC: cfe-commits Differential Revision: http://llvm-reviews.chandlerc.com/D1356 llvm-svn: 188245
-
David Majnemer authored
Summary: We need to do two things: - Initialize BSSSection in MCObjectFileInfo::InitCOFFMCObjectFileInfo - Teach TargetLoweringObjectFileCOFF::SelectSectionForGlobal what to do with it This fixes PR16861. Reviewers: rnk Reviewed By: rnk CC: llvm-commits Differential Revision: http://llvm-reviews.chandlerc.com/D1361 llvm-svn: 188244
-
Eric Christopher authored
CUs. Currently only hashes the name of CUs and the names of any children, but it's an obvious first step to show the framework. The testcase should continue to be correct, however, as it's an empty TU. llvm-svn: 188243
-
Marshall Clow authored
llvm-svn: 188242
-
Marshall Clow authored
llvm-svn: 188241
-
Sean Callanan authored
resolution of class_getSuperclass. <rdar://problem/14662686> llvm-svn: 188240
-
Peter Collingbourne authored
Differential Revision: http://llvm-reviews.chandlerc.com/D1350 llvm-svn: 188238
-
Reid Kleckner authored
llvm-svn: 188237
-
Nick Lewycky authored
to find loops if the From and To instructions were in the same block. Refactor the code a little now that we need to fill to start the CFG-walking algorithm with more than one starting basic block sometimes. Special thanks to Andrew Trick for catching an error in my understanding of natural loops in code review. llvm-svn: 188236
-
Rui Ueyama authored
This is a temporary measure because the semantics of the common symbol is actually more compilcated than the simple mergeable symbol. llvm-svn: 188235
-
Eric Christopher authored
llvm-svn: 188234
-
Eric Christopher authored
llvm-svn: 188233
-
Eric Christopher authored
llvm-svn: 188232
-
Peter Collingbourne authored
Differential Revision: http://llvm-reviews.chandlerc.com/D1348 llvm-svn: 188231
-
Reid Kleckner authored
This moves a header-only class from Sema to Analysis and puts the option check in Sema. Patch by Chris Wailes! llvm-svn: 188230
-
Peter Collingbourne authored
Differential Revision: http://llvm-reviews.chandlerc.com/D1347 llvm-svn: 188229
-
Rui Ueyama authored
After r188221, the prefix given by --check-prefix must match with the label as a whole. Substring is not considered to be a correct label anymore. llvm-svn: 188227
-
Hans Wennborg authored
Differential Revision: http://llvm-reviews.chandlerc.com/D1370 llvm-svn: 188226
-
Fariborz Jahanian authored
, currently unused, for future cf-annotation work. llvm-svn: 188224
-
Matt Arsenault authored
e.g. Use Ty->getPointerElementType() instead of cast<PointerType>(Ty)->getElementType() llvm-svn: 188223
-
David Blaikie authored
DebugInfo: Simplify declaration building code - relying on the limit debug info checking already in CreateType(RecordType) llvm-svn: 188222
-
Rui Ueyama authored
FileCheck should check to make sure the prefix was found, and not a word containing it (e.g -check-prefix=BASEREL shouldn't match NOBASEREL). Patch by Ron Ofir. llvm-svn: 188221
-
Michael J. Spencer authored
llvm-svn: 188220
-
Matt Arsenault authored
llvm-svn: 188219
-
Kevin Enderby authored
undefined and produce an error message instead as this is a non-relocatable expression with X86 Mach-O. rdar://8920876 llvm-svn: 188218
-
Peter Collingbourne authored
llvm-svn: 188217
-
Peter Collingbourne authored
llvm-svn: 188216
-
Tom Stellard authored
R600 doesn't need to do any scheduling on the SelectionDAG now that it has a very good MachineScheduler. Also, using the VLIW SelectionDAG scheduler was having a major impact on compile times. For example with the phatk kernel here are the LLVM IR to machine code compile times: With Sched::VLIW Total Compile Time: 1.4890 Seconds (User + System) SelectionDAG Instruction Scheduling: 1.1670 Seconds (User + System) With Sched::Source Total Compile Time: 0.3330 Seconds (User + System) SelectionDAG Instruction Scheduling: 0.0070 Seconds (User + System) The code ouput was identical with both schedulers. This may not be true for all programs, but it gives me confidence that there won't be much reduction, if any, in code quality by using Sched::Source. llvm-svn: 188215
-
David Blaikie authored
llvm-svn: 188214
-
Hans Wennborg authored
llvm-svn: 188213
-
Kaelyn Uhrain authored
incomplete types, courtesy of Luke Zarko. llvm-svn: 188212
-
Hans Wennborg authored
The cmake-clang-x86_64 was upset: error: 'template<class ImplClass, class RetTy> class clang::ConstStmtVisitor' used without template parameters llvm-svn: 188211
-
Hans Wennborg authored
This is used to name the linked output file. Differential Revision: http://llvm-reviews.chandlerc.com/D1344 llvm-svn: 188210
-
Eli Friedman authored
This is just a couple of minor fixes to account for the existence of ElaboratedType. llvm-svn: 188209
-
Eli Friedman authored
I'm not really satisfied with the ad-hoc nature of Sema::diagnoseQualifiedDeclaration, but I'm not sure how to fix it. Fixes <rdar://problem/14639501>. llvm-svn: 188208
-
DeLesley Hutchins authored
Reviewed by delesley, dblaikie. Add the annotations and code needed to support a basic 'consumed' analysis. Summary: This new analysis is based on academic literature on linear types. It tracks the state of a value, either as unconsumed, consumed, or unknown. Methods are then annotated as CallableWhenUnconsumed, and when an annotated method is called while the value is in the 'consumed' state a warning is issued. A value may be tested in the conditional statement of an if-statement; when this occurs we know the state of the value in the different branches, and this information is added to our analysis. The code is still highly experimental, and the names of annotations or the algorithm may be subject to change. llvm-svn: 188206
-
Michael Gottesman authored
llvm-svn: 188205
-
Shuxin Yang authored
In order to appease people (in Apple) who accuse me for committing "huge change" (?) without proper review. Thank Eric for fixing a compile-warning. llvm-svn: 188204
-