- Sep 15, 2011
-
-
Nick Lewycky authored
DW_AT_GNU_template_name = 0x2110, not 0x2108. That would explain those attr #0x2110 under the DW_TAG_GNU_template_template_param I'm seeing. Migrate from documented values to reality. llvm-svn: 139785
-
Nick Lewycky authored
1. http://gcc.gnu.org/wiki/TemplateParmsDwarf 2. ftp://ftp.software.ibm.com/software/os390/czos/dwarf/mips_extensions.pdf llvm-svn: 139784
-
Jakob Stoklund Olesen authored
There is only one legitimate use remaining, in addIntervalsForSpills(). All other calls to hasPHIKill() are only used to update PHIKill flags. The addIntervalsForSpills() function is part of the old spilling framework, only used by linearscan. llvm-svn: 139783
-
Jakob Stoklund Olesen authored
Instead, let HasOtherReachingDefs() test for defs in B that overlap any phi-defs in A as well. This test is slightly different, but almost identical. A perfectly precise test would only check those phi-defs in A that are reachable from AValNo. llvm-svn: 139782
-
Jakob Stoklund Olesen authored
The source live range is recomputed using shrinkToUses() which does handle phis correctly. The hasPHIKill() condition was relevant in the old days when ReMaterializeTrivialDef() tried to recompute the live range itself. The shrinkToUses() function will mark the original def as dead when no more uses and phi kills remain. It is then removed by runOnMachineFunction(). llvm-svn: 139781
-
Jakob Stoklund Olesen authored
It is conservatively correct to keep the hasPHIKill flags, even after deleting PHI-defs. The calculation can be very expensive after taildup has created a quadratic number of indirectbr edges in the CFG, and the hasPHIKill flag isn't used for anything after RenumberValues(). llvm-svn: 139780
-
Nick Lewycky authored
Note that DW_TAG_rvalue_reference_type is officially 0x42, not 0x41. llvm-svn: 139779
-
Benjamin Kramer authored
Thanks Nick! llvm-svn: 139778
-
Benjamin Kramer authored
llvm-svn: 139777
-
Nick Lewycky authored
llvm-svn: 139776
-
Benjamin Kramer authored
llvm-svn: 139775
-
Benjamin Kramer authored
llvm-svn: 139774
-
Benjamin Kramer authored
llvm-svn: 139773
-
Sean Callanan authored
to execute expressions even in the absence of a process. This allows expressions to run in situations where the target cannot run -- e.g., to perform calculations based on type information, or to inspect a binary's static data. This modification touches the following files: lldb-private-enumerations.h Introduce a new enum specifying the policy for processing an expression. Some expressions should always be JITted, for example if they are functions that will be used over and over again. Some expressions should always be interpreted, for example if the target is unsafe to run. For most, it is acceptable to JIT them, but interpretation is preferable when possible. Target.[h,cpp] Have EvaluateExpression now accept the new enum. ClangExpressionDeclMap.[cpp,h] Add support for the IR interpreter and also make the ClangExpressionDeclMap more robust in the absence of a process. ClangFunction.[cpp,h] Add support for the new enum. IRInterpreter.[cpp,h] New implementation. ClangUserExpression.[cpp,h] Add support for the new enum, and for running expressions in the absence of a process. ClangExpression.h Remove references to the old DWARF-based method of evaluating expressions, because it has been superseded for now. ClangUtilityFunction.[cpp,h] Add support for the new enum. ClangExpressionParser.[cpp,h] Add support for the new enum, remove references to DWARF, and add support for checking whether the expression could be evaluated statically. IRForTarget.[h,cpp] Add support for the new enum, and add utility functions to support the interpreter. IRToDWARF.cpp Removed CommandObjectExpression.cpp Remove references to the obsolete -i option. Process.cpp Modify calls to ClangUserExpression::Evaluate to pass the correct enum (for dlopen/dlclose) SBValue.cpp Add support for the new enum. SBFrame.cpp Add support for he new enum. BreakpointOptions.cpp Add support for the new enum. llvm-svn: 139772
-
Benjamin Kramer authored
The llvm-dwarfdump output isn't very verbose yet. llvm-svn: 139771
-
John McCall authored
llvm-svn: 139770
-
John McCall authored
we don't need to. llvm-svn: 139769
-
Eli Friedman authored
llvm-svn: 139768
-
Johnny Chen authored
the passed in (MachException::Data &)exc first before possible reassignment of the member m_stop_exception with exc. This allows lldb to stop at the watchpoint of a simple test program. llvm-svn: 139767
-
Jim Ingham authored
Take out all the separate places in Attach where we were getting the target architecture, and move that but of functionality into CompleteAttach. llvm-svn: 139766
-
Andrew Trick authored
An improper SlotIndex->VNInfo lookup was leading to unsafe copy removal. Fixes PR10920 401.bzip2 miscompile with no IV rewrite. llvm-svn: 139765
-
Jim Ingham authored
Change the "attach" command to always wait synchronously for the target to stop. It's not very useful to return the prompt in mid-attach, and it makes reporting the result of the attach hard to do. llvm-svn: 139764
-
Anna Zaks authored
[analyzer] Refactor: make PathDiagnosticLocation responsible for validation of SourceLocations (commit 2 of ?): - Modify all PathDiagnosticLocation constructors that take Stmt to also requre LocationContext. - Add a constructor which should be used in case there is no valid statement/location (it will grab the location of the enclosing function). llvm-svn: 139763
-
Jim Ingham authored
Fix ArchSpec::operator== to take the Triple into account as well as the Core. Also make the constructors explicit. llvm-svn: 139762
-
Jim Ingham authored
Fix ArchSpec::operator== to take the Triple into account as well as the Core. Also make the constructors explicit. llvm-svn: 139761
-
Jason Molenda authored
Have the FuncUnwinder object request & provide an architecture-defined UnwindPlan for unwinding from the first instruction of an otherwise unknown function call (GetUnwindPlanArchitectureDefaultAtFunctionEntry()). Update RegisterContextLLDB::GetFullUnwindPlanForFrame() to detect the case of a frame 0 at address 0x0 which indicates that we jumped through a NULL function pointer. Use the ABI's FunctionEntryUnwindPlan to find the caller frame. These changes make it so lldb can identify the calling frame correctly in code like int main () { void (*f)(void) = 0; f(); } llvm-svn: 139760
-
Greg Clayton authored
llvm-svn: 139759
-
Eli Friedman authored
Fix the code creating VZEXT_LOAD so that it creates the right memoperand. Issue spotted in -debug output. I can't think of any practical effects at the moment, but it might matter if we start doing more aggressive alias analysis in CodeGen. llvm-svn: 139758
-
Jim Grosbach authored
llvm-svn: 139757
-
Jim Grosbach authored
llvm-svn: 139756
-
Douglas Gregor authored
will ignore the erasedOnReboot option, and properly escape the backslash in "C:\TEMP". Thanks to Aaron and Francois. llvm-svn: 139755
-
Jim Grosbach authored
llvm-svn: 139754
-
Jim Grosbach authored
llvm-svn: 139753
-
Devang Patel authored
llvm-svn: 139752
-
Devang Patel authored
llvm-svn: 139751
-
Douglas Gregor authored
llvm-svn: 139750
-
Jim Grosbach authored
llvm-svn: 139748
-
Owen Anderson authored
llvm-svn: 139747
-
Johnny Chen authored
llvm-svn: 139746
-
Douglas Gregor authored
Don't try to write a macro offset for an identifier that names a non-exported macro, for real this time llvm-svn: 139745
-