- Feb 15, 2012
-
-
Andrew Trick authored
Added TargetPassConfig::disablePass/substitutePass as a general mechanism to override specific passes. llvm-svn: 150562
-
Andrew Trick authored
llvm-svn: 150561
-
Richard Smith authored
expression is referenced, defined, then referenced again, make sure we instantiate it the second time it's referenced. This is the static data member analogue of r150518. llvm-svn: 150560
-
Enrico Granata authored
llvm-svn: 150559
-
rdar://problem/10062621Enrico Granata authored
New public API for handling formatters: creating, deleting, modifying categories, and formatters, and managing type/formatter association. This provides SB classes for each of the main object types involved in providing formatter support: SBTypeCategory SBTypeFilter SBTypeFormat SBTypeSummary SBTypeSynthetic plus, an SBTypeNameSpecifier class that is used on the public API layer to abstract the notion that formatters can be applied to plain type-names as well as to regular expressions For naming consistency, this patch also renames a lot of formatters-related classes. Plus, the changes in how flags are handled that started with summaries is now extended to other classes as well. A new enum (lldb::eTypeOption) is meant to support this on the public side. The patch also adds several new calls to the formatter infrastructure that are used to implement by-index accessing and several other design changes required to accommodate the new API layer. An architectural change is introduced in that backing objects for formatters now become writable. On the public API layer, CoW is implemented to prevent unwanted propagation of changes. Lastly, there are some modifications in how the "default" category is constructed and managed in relation to other categories. llvm-svn: 150558
-
Richard Smith authored
to be core constant expressions (including pointers and references to temporaries), and makes constexpr calculations Turing-complete. A Turing machine simulator is included as a testcase. This opens up the possibilty of removing CCValue entirely, and removing some copies from the constant evaluator in the process, but that cleanup is not part of this change. llvm-svn: 150557
-
Anna Zaks authored
llvm-svn: 150556
-
Richard Smith authored
llvm-svn: 150555
-
Sean Callanan authored
JIT when printing the values of registers (e.g., "expr $pc"). Now the expression parser can do this in the IR interpreter without running code in the inferior process. llvm-svn: 150554
-
Lang Hames authored
llvm-svn: 150553
-
Lang Hames authored
llvm-svn: 150552
-
John McCall authored
is general goodness because representations of member pointers are not always equivalent across member pointer types on all ABIs (even though this isn't really standard-endorsed). Take advantage of the new information to teach IR-generation how to do these reinterprets in constant initializers. Make sure this works when intermingled with hierarchy conversions (although this is not part of our motivating use case). Doing this in the constant-evaluator would probably have been better, but that would require a *lot* of extra structure in the representation of constant member pointers: you'd really have to track an arbitrary chain of hierarchy conversions and reinterpretations in order to get this right. Ultimately, this seems less complex. I also wasn't quite sure how to extend the constant evaluator to handle foldings that we don't actually want to treat as extended constant expressions. llvm-svn: 150551
-
Pete Cooper authored
llvm-svn: 150550
-
Douglas Gregor authored
well as improving the RecursiveASTVisitor's walk of lambda expressions. llvm-svn: 150549
-
Fariborz Jahanian authored
meta-data. llvm-svn: 150548
-
Nick Kledzik authored
llvm-svn: 150547
-
Howard Hinnant authored
llvm-svn: 150542
-
Nick Kledzik authored
llvm-svn: 150539
-
Chad Rosier authored
llvm-svn: 150538
-
Pete Cooper authored
Stop custom lowering forr x86 DEC64m from happening if the load in the lowered sequence has more than 1 user llvm-svn: 150537
-
Chad Rosier authored
llvm-svn: 150536
-
Anna Zaks authored
llvm-svn: 150535
-
Anna Zaks authored
llvm-svn: 150534
-
Anna Zaks authored
the passed in pointer on failure. llvm-svn: 150533
-
Anna Zaks authored
hardening. llvm-svn: 150532
-
Jakob Stoklund Olesen authored
Pretend that regmask interference ends at the 'dead' slot, even when there is other interference ending at the 'reg' slot of the same instruction. llvm-svn: 150531
-
Jakob Stoklund Olesen authored
Perform all comparisons at instruction granularity, and make sure register masks on uses count in both gaps. llvm-svn: 150530
-
Jakob Stoklund Olesen authored
Only accept register masks when looking for an 'overlapping' def. When Overlap is not set, the function searches for a proper definition of Reg. This means MI->modifiesRegister() considers register masks, but MI->definesRegister() doesn't. llvm-svn: 150529
-
Jakob Stoklund Olesen authored
When a physreg is live in to a basic block, look for any instruction in the block that clobbers the physreg. The instruction doesn't have to properly redefine the register, any overlapping clobber is OK. This slightly changes live ranges when compiling with register masks. llvm-svn: 150528
-
Jakob Stoklund Olesen authored
The old DenseMap hashed order was very confusing. llvm-svn: 150527
-
Richard Smith authored
Conditionally include headers which older STL implementations don't provide. llvm-svn: 150526
-
Lang Hames authored
llvm-svn: 150525
-
- Feb 14, 2012
-
-
Richard Smith authored
llvm-svn: 150524
-
Sean Callanan authored
can be allocated in the process. llvm-svn: 150523
-
Richard Smith authored
features. :) llvm-svn: 150522
-
Richard Smith authored
llvm-svn: 150521
-
Chad Rosier authored
llvm-svn: 150520
-
Douglas Gregor authored
lambda expressions. Because these issue was pulled back from Ready status at the Kona meeting, we still emit an ExtWarn when using default arguments for lambda expressions. llvm-svn: 150519
-
Richard Smith authored
template is defined, and then the specialization is referenced again, don't forget to instantiate the template on the second reference. Use the source location of the first reference as the point of instantiation, though. llvm-svn: 150518
-
Argyrios Kyrtzidis authored
llvm-svn: 150517
-