- Feb 06, 2012
-
-
Abramo Bagnara authored
llvm-svn: 149868
-
Peter Collingbourne authored
llvm-svn: 149867
-
Benjamin Kramer authored
llvm-svn: 149866
-
Benjamin Kramer authored
llvm-svn: 149865
-
Benjamin Kramer authored
llvm-svn: 149864
-
Benjamin Kramer authored
Reorder includes while at it. llvm-svn: 149863
-
Craig Topper authored
llvm-svn: 149862
-
Nick Lewycky authored
change. llvm-svn: 149861
-
Craig Topper authored
Move some llvm_unreachable's from r149849 out of switch statements to satisfy -Wcovered-switch-default llvm-svn: 149860
-
Craig Topper authored
llvm-svn: 149859
-
Greg Clayton authored
working, but not functions). I need to check on a few things to make sure I am registering everything correctly in the right order and in the right contexts. llvm-svn: 149858
-
Sebastian Pop authored
llvm-svn: 149857
-
Sebastian Pop authored
llvm-svn: 149856
-
Craig Topper authored
Fix vector splat casts to cast element to the appropriate vector element before inserting into the vector. Fixes PR11930. llvm-svn: 149855
-
Richard Smith authored
llvm-svn: 149854
-
Greg Clayton authored
interface (.i) files for each class. Changed the FindFunction class from: uint32_t SBTarget::FindFunctions (const char *name, uint32_t name_type_mask, bool append, lldb::SBSymbolContextList& sc_list) uint32_t SBModule::FindFunctions (const char *name, uint32_t name_type_mask, bool append, lldb::SBSymbolContextList& sc_list) To: lldb::SBSymbolContextList SBTarget::FindFunctions (const char *name, uint32_t name_type_mask = lldb::eFunctionNameTypeAny); lldb::SBSymbolContextList SBModule::FindFunctions (const char *name, uint32_t name_type_mask = lldb::eFunctionNameTypeAny); This makes the API easier to use from python. Also added the ability to append a SBSymbolContext or a SBSymbolContextList to a SBSymbolContextList. Exposed properties for lldb.SBSymbolContextList in python: lldb.SBSymbolContextList.modules => list() or all lldb.SBModule objects in the list lldb.SBSymbolContextList.compile_units => list() or all lldb.SBCompileUnits objects in the list lldb.SBSymbolContextList.functions => list() or all lldb.SBFunction objects in the list lldb.SBSymbolContextList.blocks => list() or all lldb.SBBlock objects in the list lldb.SBSymbolContextList.line_entries => list() or all lldb.SBLineEntry objects in the list lldb.SBSymbolContextList.symbols => list() or all lldb.SBSymbol objects in the list This allows a call to the SBTarget::FindFunctions(...) and SBModule::FindFunctions(...) and then the result can be used to extract the desired information: sc_list = lldb.target.FindFunctions("erase") for function in sc_list.functions: print function for symbol in sc_list.symbols: print symbol Exposed properties for the lldb.SBSymbolContext objects in python: lldb.SBSymbolContext.module => lldb.SBModule lldb.SBSymbolContext.compile_unit => lldb.SBCompileUnit lldb.SBSymbolContext.function => lldb.SBFunction lldb.SBSymbolContext.block => lldb.SBBlock lldb.SBSymbolContext.line_entry => lldb.SBLineEntry lldb.SBSymbolContext.symbol => lldb.SBSymbol Exposed properties for the lldb.SBBlock objects in python: lldb.SBBlock.parent => lldb.SBBlock for the parent block that contains lldb.SBBlock.sibling => lldb.SBBlock for the sibling block to the current block lldb.SBBlock.first_child => lldb.SBBlock for the first child block to the current block lldb.SBBlock.call_site => for inline functions, return a lldb.declaration object that gives the call site file, line and column lldb.SBBlock.name => for inline functions this is the name of the inline function that this block represents lldb.SBBlock.inlined_block => returns the inlined function block that contains this block (might return itself if the current block is an inlined block) lldb.SBBlock.range[int] => access the address ranges for a block by index, a list() with start and end address is returned lldb.SBBlock.ranges => an array or all address ranges for this block lldb.SBBlock.num_ranges => the number of address ranges for this blcok SBFunction objects can now get the SBType and the SBBlock that represents the top scope of the function. SBBlock objects can now get the variable list from the current block. The value list returned allows varaibles to be viewed prior with no process if code wants to check the variables in a function. There are two ways to get a variable list from a SBBlock: lldb::SBValueList SBBlock::GetVariables (lldb::SBFrame& frame, bool arguments, bool locals, bool statics, lldb::DynamicValueType use_dynamic); lldb::SBValueList SBBlock::GetVariables (lldb::SBTarget& target, bool arguments, bool locals, bool statics); When a SBFrame is used, the values returned will be locked down to the frame and the values will be evaluated in the context of that frame. When a SBTarget is used, global an static variables can be viewed without a running process. llvm-svn: 149853
-
Aaron Ballman authored
llvm-svn: 149852
-
- Feb 05, 2012
-
-
Benjamin Kramer authored
llvm-svn: 149851
-
Benjamin Kramer authored
llvm-svn: 149850
-
Craig Topper authored
llvm-svn: 149849
-
Talin authored
llvm-svn: 149848
-
Nick Lewycky authored
* Most of the transforms come through intact by having each transformed load or store copy the ordering and synchronization scope of the original. * The transform that turns a global only accessed in main() into an alloca (since main is non-recursive) with a store of the initial value uses an unordered store, since it's guaranteed to be the first thing to happen in main. (Threads may have started before main (!) but they can't have the address of a function local before the point in the entry block we insert our code.) * The heap-SRoA transforms are disabled in the face of atomic operations. This can probably be improved; it seems odd to have atomic accesses to an alloca that doesn't have its address taken. AnalyzeGlobal keeps track of the strongest ordering found in any use of the global. This is more information than we need right now, but it's cheap to compute and likely to be useful. llvm-svn: 149847
-
Evan Cheng authored
llvm-svn: 149846
-
Nick Lewycky authored
llvm-svn: 149845
-
Aaron Ballman authored
llvm-svn: 149844
-
Duncan Sands authored
predecessor then it's Src. llvm-svn: 149843
-
Gregory Szorc authored
llvm-svn: 149842
-
Duncan Sands authored
above. llvm-svn: 149841
-
Duncan Sands authored
by GCC). llvm-svn: 149840
-
Duncan Sands authored
llvm-svn: 149839
-
Duncan Sands authored
logic by half: isOnlyReachableViaThisEdge was trying to be clever and handle the case of a branch to a basic block which is contained in a loop. This costs a domtree lookup and is completely useless due to GVN's position in the pass pipeline: all loops have preheaders at this point, which means it is enough for isOnlyReachableViaThisEdge to check that Dst has only one predecessor. (I checked this theoretical argument by running over the entire nightly testsuite, and indeed it is so!). llvm-svn: 149838
-
Duncan Sands authored
compiling sqlite3, by only doing dom queries after the cheap check rather than interleaved with it. llvm-svn: 149836
-
Duncan Sands authored
llvm-svn: 149834
-
Duncan Sands authored
llvm-svn: 149833
-
Duncan Sands authored
llvm-svn: 149832
-
Tobias Grosser authored
Names that have corresponding classes in python are commonly started with an uppercase letter. Let's follow that convention. llvm-svn: 149831
-
Tobias Grosser authored
Contributed by: Gregory Szorc <gregory.szorc@gmail.com> llvm-svn: 149830
-
Tobias Grosser authored
Contributed by: Gregory Szorc <gregory.szorc@gmail.com> llvm-svn: 149829
-
Tobias Grosser authored
Added a missing enumeration. Contributed by: Gregory Szorc <gregory.szorc@gmail.com> llvm-svn: 149828
-
Tobias Grosser authored
Contributed by: Gregory Szorc <gregory.szorc@gmail.com> llvm-svn: 149827
-