- May 11, 2013
-
-
Benjamin Kramer authored
Adding attributes to a uniqued set has become expensive, don't do it more often than necessary. No functionality change. llvm-svn: 181662
-
David Majnemer authored
Use isKnownToBeAPowerOfTwo in visitUrem so that we may more aggressively fold away urem instructions. llvm-svn: 181661
-
Simon Atanasyan authored
llvm-svn: 181660
-
Richard Smith authored
we loaded from PCH, if we're building another PCH, create an update record to patch the return type of the earlier declaration. llvm-svn: 181659
-
Jason Molenda authored
names when specifying the DynamicLoaderDarwinKernel. ProcessGDBRemote wasn't setting the dyld string any more; remove the remaining code tracking the dyld plugin name altogether from that process plugin. llvm-svn: 181658
-
Rafael Espindola authored
To add a frame now there is a dedicated addFrameMove which also takes care of constructing the move itself. llvm-svn: 181657
-
Rafael Espindola authored
llvm-svn: 181656
-
Rui Ueyama authored
llvm-svn: 181655
-
Reed Kotler authored
not think it can support small data sections. llvm-svn: 181654
-
Jason Molenda authored
Don't want about being unable to find a needed objective-c runtime function when we're core file debugging and can't jit anything anyway. Don't warn when quitting a debug session on a core file, the program state can be reconstructed by re-running lldb on the same core file again. llvm-svn: 181653
-
Rui Ueyama authored
llvm-svn: 181652
-
rdar://problem/13700260Greg Clayton authored
Avoid a deadlock when using the OperatingSystemPython code and typing "process interrupt". There was a possible lock inversion between the target API lock and the process' thread list lock due to code trying to discard the thread list. This was fixed by adding a boolean to Process::Halt() that indicates if the thread plans should be discarded and doing it in the private state thread when we process the stopped state. llvm-svn: 181651
-
David Blaikie authored
Eric's code review feedback to r181644 llvm-svn: 181650
-
Rafael Espindola authored
llvm-svn: 181649
-
Nadav Rotem authored
For example: bar() { int a = A[i]; int b = A[i+1]; B[i] = a; B[i+1] = b; foo(a); <--- a is used outside the vectorized expression. } llvm-svn: 181648
-
Nadav Rotem authored
llvm-svn: 181647
-
Nadav Rotem authored
llvm-svn: 181646
-
Matt Kopec authored
Use mangled and demangled names when checking for a function in a namespace and a function in an anonymous namespace, respectively. llvm-svn: 181645
-
David Blaikie authored
We could support the GCC extension DW_TAG_GNU_template_parameter_pack if we're feeling adventurous, at some point - but I don't think GDB's doing anything useful with it yet anyway. llvm-svn: 181644
-
Douglas Gregor authored
[Modules] Make r180934 more efficient by only loading top-level module maps in system header directories. llvm-svn: 181643
-
Reed Kotler authored
mips16/mips32 floating point interoperability. This patch fixes returns from mips16 functions so that if the function was in fact called by a mips32 hard float routine, then values that would have been returned in floating point registers are so returned. Mips16 mode has no floating point instructions so there is no way to load values into floating point registers. This is needed when returning float, double, single complex, double complex in the Mips ABI. Helper functions in libc for mips16 are available to do this. For efficiency purposes, these helper functions have a different calling convention from normal Mips calls. Registers v0,v1,a0,a1 are used to pass parameters instead of a0,a1,a2,a3. This is because v0,v1,a0,a1 are the natural registers used to return floating point values in soft float. These values can then be moved to the appropriate floating point registers with no extra cost. The only register that is modified is ra in this call. The helper functions make sure that the return values are in the floating point registers that they would be in if soft float was not in effect (which it is for mips16, though the soft float is implemented using a mips32 library that uses hard float). llvm-svn: 181641
-
Rui Ueyama authored
llvm-svn: 181640
-
Jordan Rose authored
Previously, BitstreamCursor read an abbreviated record by splatting the whole thing into a data vector, then extracting and removing the /first/ element. Now, it reads the first element--the record code--separately from the actual field values. No (intended) functionality change. llvm-svn: 181639
-
Douglas Gregor authored
Sometimes people hack on their system headers. In such cases, they'll need to delete their module cache, but may not know where it is. Add a note to show them where it is. llvm-svn: 181638
-
David Blaikie authored
llvm-svn: 181637
-
- May 10, 2013
-
-
Sean Callanan authored
passed to breakpoints. <rdar://problem/13853205> llvm-svn: 181636
-
Douglas Gregor authored
Fixes <rdar://problem/13856838>. llvm-svn: 181635
-
David Blaikie authored
* Provide DW_TAG_template_value_parameter for pointers, function pointers, member pointers, and member function pointers (still missing support for template template parameters which GCC encodes as a DW_TAG_GNU_template_template_param) * Provide values for all but the (member & non-member) function pointer case. Simple constant integer values for member pointers (offset within the object) and address for the value pointer case. GCC doesn't provide a value for the member function pointer case so I'm not sure how, if at all, GDB supports encoding that. & non-member function pointers should follow shortly in a subsequent patch. * Null pointer value encodings of all of these types, including correctly encoding null data member pointers as -1. llvm-svn: 181634
-
David Blaikie authored
This is only tested for global variables at the moment (& includes tests for the unnamed parameter case, since apparently this entire function was completely untested previously) llvm-svn: 181632
-
rdar://problem/13854277Greg Clayton authored
<rdar://problem/13594769> Main changes in this patch include: - cleanup plug-in interface and use ConstStrings for plug-in names - Modfiied the BSD Archive plug-in to be able to pick out the correct .o file when .a files contain multiple .o files with the same name by using the timestamp - Modified SymbolFileDWARFDebugMap to properly verify the timestamp on .o files it loads to ensure we don't load updated .o files and cause problems when debugging The plug-in interface changes: Modified the lldb_private::PluginInterface class that all plug-ins inherit from: Changed: virtual const char * GetPluginName() = 0; To: virtual ConstString GetPluginName() = 0; Removed: virtual const char * GetShortPluginName() = 0; - Fixed up all plug-in to adhere to the new interface and to return lldb_private::ConstString values for the plug-in names. - Fixed all plug-ins to return simple names with no prefixes. Some plug-ins had prefixes and most ones didn't, so now they all don't have prefixed names, just simple names like "linux", "gdb-remote", etc. llvm-svn: 181631
-
Jyotsna Verma authored
Earlier, this variable was used in an assert and was causing failure on darwin. llvm-svn: 181630
-
Adrian Prantl authored
a related type (e.g., if they use the instancetype keyword). rdar://problem/13359718 llvm-svn: 181629
-
Jyotsna Verma authored
No functionality change. llvm-svn: 181628
-
Enea Zaffanella authored
llvm-svn: 181627
-
Richard Smith authored
and misclassify it as a complex-real conversion. llvm-svn: 181626
-
Jyotsna Verma authored
llvm-svn: 181624
-
Shankar Easwaran authored
llvm-svn: 181622
-
Rafael Espindola authored
llvm-svn: 181621
-
Chad Rosier authored
The issue was that the MatchingInlineAsm and VariantID args to the MatchInstructionImpl function weren't being set properly. Specifically, when parsing intel syntax, the parser thought it was parsing inline assembly in the at&t dialect; that will never be the case. The crash was caused when the emitter tried to emit the instruction, but the operands weren't set. When parsing inline assembly we only set the opcode, not the operands, which is used to lookup the instruction descriptor. rdar://13854391 and PR15945 Also, this commit reverts r176036. Now that we're correctly parsing the intel syntax the pushad/popad don't match properly. I've reimplemented that fix using a MnemonicAlias. llvm-svn: 181620
-
Rafael Espindola authored
llvm-svn: 181618
-