- Oct 12, 2012
-
-
rdar://problem/12042500Greg Clayton authored
Fixed an issue where we would try to launch an application twice and the second failure would cover up the first. llvm-svn: 165756
-
Greg Clayton authored
llvm-svn: 165755
-
Sean Callanan authored
change in the LLDB target data API. llvm-svn: 165754
-
- Oct 11, 2012
-
-
Jan Wen Voung authored
llvm-svn: 165753
-
Chad Rosier authored
reimplemented in the AsmParser where it belongs. llvm-svn: 165752
-
Chad Rosier authored
now unused static helper function. The test case needs to be remove temporarily until I can better filter memory operands that aren't actual variable reference. llvm-svn: 165751
-
Micah Villmow authored
llvm-svn: 165747
-
Douglas Gregor authored
only with modules, when two disjoint modules #define the same identifier to different token sequences. llvm-svn: 165746
-
Ted Kremenek authored
llvm-svn: 165744
-
Ted Kremenek authored
objc_atomicCompareAndSwap. llvm-svn: 165743
-
Ted Kremenek authored
llvm-svn: 165742
-
Nadav Rotem authored
llvm-svn: 165741
-
Greg Clayton authored
Fixed an indentation issue that only shows up when dumping .o files that use linked addresses (DWARF in .o files with debug map). llvm-svn: 165740
-
Jan Wen Voung authored
to the instruction position. The old encoding would give an absolute ID which counts up within a function, and only resets at the next function. I.e., Instead of having: ... = icmp eq i32 n-1, n-2 br i1 ..., label %bb1, label %bb2 it will now be roughly: ... = icmp eq i32 1, 2 br i1 1, label %bb1, label %bb2 This makes it so that ids remain relatively small and can be encoded in fewer bits. With this encoding, forward reference operands will be given negative-valued IDs. Use signed VBRs for the most common case of forward references, which is phi instructions. To retain backward compatibility we bump the bitcode version from 0 to 1 to distinguish between the different encodings. llvm-svn: 165739
-
Manuel Klimek authored
llvm-svn: 165736
-
Argyrios Kyrtzidis authored
in c-index-test. index_enteredMainFile is not invoked when indexing a module file. llvm-svn: 165735
-
Argyrios Kyrtzidis authored
llvm-svn: 165734
-
Ted Kremenek authored
llvm-svn: 165733
-
Argyrios Kyrtzidis authored
llvm-svn: 165732
-
Derek Schuff authored
llvm-svn: 165731
-
rdar://problem/12331741Greg Clayton authored
Dynamic type code must be efficient and fast. Now it is. Added ObjC v1 support for getting the complete list of ISA values. The main flow of the AppleObjCRuntime subclasses is now they must override "virtual bool UpdateISAToDescriptorMap_Impl();". This function will update the complete list of ISA values and create ClassDescriptorSP objects for each one. Now we have the complete list of valid ISA values which we can use for verification when doing dynamic typing. Refactored a bunch of stuff so that the AppleObjCRuntime subclasses don't have to implement as many functions as they used to. llvm-svn: 165730
-
Douglas Gregor authored
associated with deserializing macro history for an identifier. llvm-svn: 165729
-
Greg Clayton authored
llvm-svn: 165728
-
Douglas Gregor authored
llvm-svn: 165727
-
Micah Villmow authored
Add in the first iteration of support for llvm/clang/lldb to allow variable per address space pointer sizes to be optimized correctly. llvm-svn: 165726
-
Jordan Rose authored
Fix-up for r165718, should get the buildbots back online. llvm-svn: 165723
-
Derek Schuff authored
with x86/ARM architecture llvm-svn: 165722
-
Jakob Stoklund Olesen authored
Not all instructions define a virtual register in their first operand. Specifically, INLINEASM has a different format. <rdar://problem/12472811> llvm-svn: 165721
-
Rafael Espindola authored
Grosser. llvm-svn: 165720
-
Jordan Rose authored
This is a "safe" pattern, or at least one that cannot be helped by using a strong local variable. However, if the single read is within a loop, it should /always/ be treated as potentially dangerous. <rdar://problem/12437490> llvm-svn: 165719
-
Jordan Rose authored
Previously, [foo weakProp] was not being treated the same as foo.weakProp. Now, for every explicit message send, we check if it's a property access, and if so, if the property is weak. Then for every assignment of a message, we have to do the same thing again. This is a potentially expensive increase because determining whether a method is a property accessor requires searching through the methods it overrides. However, without it -Warc-repeated-use-of-weak will miss cases from people who prefer not to use dot syntax. If this turns out to be too expensive, we can try caching the result somewhere, or even lose precision by not checking superclass methods. The warning is off-by-default, though. <rdar://problem/12407765> llvm-svn: 165718
-
Argyrios Kyrtzidis authored
The ASTUnit needs to initialize an ASTWriter at the beginning of parsing to fully handle serialization of a translation unit that imports modules. Do this by introducing an option to enable it, which corresponds to CXTranslationUnit_ForSerialization on the C API side. llvm-svn: 165717
-
Jordan Rose authored
Currently, Objective-C does not support class properties, even though it allows calling class methods with dot syntax. No intended functionality change; purely optimization. llvm-svn: 165716
-
Derek Schuff authored
and Native Client llvm-svn: 165715
-
Bill Schmidt authored
For function calls on the 64-bit PowerPC SVR4 target, each parameter is mapped to as many doublewords in the parameter save area as necessary to hold the parameter. The first 13 non-varargs floating-point values are passed in registers; any additional floating-point parameters are passed in the parameter save area. A single-precision floating-point parameter (32 bits) must be mapped to the second (rightmost, low-order) word of its assigned doubleword slot. Currently LLVM violates this ABI requirement by mapping such a parameter to the first (leftmost, high-order) word of its assigned doubleword slot. This is internally self-consistent but will not interoperate correctly with libraries compiled with an ABI-compliant compiler. This patch corrects the problem by adjusting the parameter addressing on both sides of the calling convention. llvm-svn: 165714
-
David Chisnall authored
llvm-svn: 165713
-
NAKAMURA Takumi authored
llvm-svn: 165712
-
David Chisnall authored
Note: [D]M{T,F}CP2 is just a recommended encoding. Vendors often provide a custom CP2 that interprets instructions differently and may wish to add their own instructions that use this opcode. We should ensure that this is easy to do. I will probably add a 'has custom CP{0-3}' subtarget flag to make this easy: We want to avoid the GCC situation where every MIPS vendor makes a custom fork that breaks every other MIPS CPU and so can't be merged upstream. llvm-svn: 165711
-
Nico Weber authored
llvm-svn: 165710
-
NAKAMURA Takumi authored
llvm-svn: 165709
-