| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
|
|
| |
declaration, determine whether the declaration will end up declaring a
function using semantic criteria (e.g., it will have function type)
rather than purely syntactic criteria (e.g., it has the form of a
function declarator). Fixes <rdar://problem/9670557>.
llvm-svn: 133854
|
| |
|
|
| |
llvm-svn: 133853
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
inspection of namespaces in the expression parser.
ClangExpressionDeclMap hitherto reported that namespaces had
been completely imported, even though the namespaces are
returned empty. To deal with this situation, ClangASTSource
was recently extended with an API to complete incomplete type
definitions, and, for greater efficiency, to complete these
definitions partially, returning only those objects that have
a given name.
This commit supports these APIs on LLDB's side, and uses it
to provide information on types resident in namespaces.
Namespaces are now imported as they were -- that is to say,
empty -- but with minimal import mode on. This means that
Clang will come back and request their contents by name as
needed. We now respond with information on the contained
types; this will be followed soon by information on functions
and variables.
llvm-svn: 133852
|
| |
|
|
| |
llvm-svn: 133851
|
| |
|
|
| |
llvm-svn: 133850
|
| |
|
|
|
|
|
|
|
| |
to turn off warning on those properties which follow Cocoa naming
convention for retaining objects and yet they were not meant for
such purposes. Also, perform consistancy checking for declared
getters of such methods. // rdar://9636091
llvm-svn: 133849
|
| |
|
|
| |
llvm-svn: 133848
|
| |
|
|
| |
llvm-svn: 133847
|
| |
|
|
| |
llvm-svn: 133846
|
| |
|
|
| |
llvm-svn: 133845
|
| |
|
|
|
|
|
|
|
| |
Move the target-specific RecordRelocation logic out of the generic MC
MachObjectWriter and into the target-specific object writers. This allows
nuking quite a bit of target knowledge from the supposedly target-independent
bits in lib/MC.
llvm-svn: 133844
|
| |
|
|
| |
llvm-svn: 133843
|
| |
|
|
| |
llvm-svn: 133842
|
| |
|
|
| |
llvm-svn: 133841
|
| |
|
|
|
|
|
| |
in the variable to an inline asm which gets run when the variable
goes out of scope.
llvm-svn: 133840
|
| |
|
|
| |
llvm-svn: 133839
|
| |
|
|
|
|
| |
performs type propagation for EXTRACT_SUBREG.
llvm-svn: 133838
|
| |
|
|
| |
llvm-svn: 133837
|
| |
|
|
| |
llvm-svn: 133836
|
| |
|
|
|
|
|
| |
We now check with the platform to see if we are doing local or remote
debugging and setup the stdio accordingly.
llvm-svn: 133835
|
| |
|
|
| |
llvm-svn: 133834
|
| |
|
|
|
|
|
|
| |
Sorry, this was a bad idea. Within clang these builtins are in a separate
"ARM" namespace, but the actual builtin names should clearly distinguish tha
they are target specific.
llvm-svn: 133833
|
| |
|
|
|
|
|
|
| |
Sorry, this was a bad idea. Within clang these builtins are in a separate
"ARM" namespace, but the actual builtin names should clearly distinguish that
they are target specific.
llvm-svn: 133832
|
| |
|
|
| |
llvm-svn: 133831
|
| |
|
|
| |
llvm-svn: 133830
|
| |
|
|
| |
llvm-svn: 133829
|
| |
|
|
| |
llvm-svn: 133828
|
| |
|
|
|
|
|
| |
not sizes; so that we use well-typed allocas; and so that we
properly recurse through the full set of variably-modified types.
llvm-svn: 133827
|
| |
|
|
| |
llvm-svn: 133826
|
| |
|
|
| |
llvm-svn: 133825
|
| |
|
|
|
|
| |
overheads. No functional change intended.
llvm-svn: 133824
|
| |
|
|
| |
llvm-svn: 133823
|
| |
|
|
| |
llvm-svn: 133822
|
| |
|
|
| |
llvm-svn: 133821
|
| |
|
|
|
|
|
|
| |
routines.
- Rename TargetRegisterDesc to MCRegisterDesc.
llvm-svn: 133820
|
| |
|
|
|
|
| |
is not implemented. // rdar://9651605
llvm-svn: 133819
|
| |
|
|
|
|
|
|
|
|
| |
The fixup value comes in as the whole 32-bit value, so for the lo16 fixup,
the upper bits need to be masked off. Previously we assumed the masking had
already been done and asserted.
rdar://9635991
llvm-svn: 133818
|
| |
|
|
|
|
|
| |
making unsafe assignment of a retainable
object, Per John's request.
llvm-svn: 133817
|
| |
|
|
|
|
| |
Fixes crash in http://llvm.org/PR10109 & rdar://9584039.
llvm-svn: 133816
|
| |
|
|
| |
llvm-svn: 133815
|
| |
|
|
|
|
| |
The i8 type is required for boolean values, but can only use ld, st and mov instructions. The i1 type continues to be used for predicates.
llvm-svn: 133814
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
instructions can be used to match combinations of multiply/divide and VCVT
(between floating-point and integer, Advanced SIMD). Basically the VCVT
immediate operand that specifies the number of fraction bits corresponds to a
floating-point multiply or divide by the corresponding power of 2.
For example, VCVT (floating-point to fixed-point, Advanced SIMD) can replace a
combination of VMUL and VCVT (floating-point to integer) as follows:
Example (assume d17 = <float 8.000000e+00, float 8.000000e+00>):
vmul.f32 d16, d17, d16
vcvt.s32.f32 d16, d16
becomes:
vcvt.s32.f32 d16, d16, #3
Similarly, VCVT (fixed-point to floating-point, Advanced SIMD) can replace a
combinations of VCVT (integer to floating-point) and VDIV as follows:
Example (assume d17 = <float 8.000000e+00, float 8.000000e+00>):
vcvt.f32.s32 d16, d16
vdiv.f32 d16, d17, d16
becomes:
vcvt.f32.s32 d16, d16, #3
llvm-svn: 133813
|
| |
|
|
|
|
|
|
|
|
| |
.file and .loc directives.
Ideally, we would utilize the existing support in AsmPrinter for this, but
I cannot find a way to get .file and .loc directives to print without the
rest of the associated DWARF sections, which ptxas cannot handle.
llvm-svn: 133812
|
| |
|
|
|
|
|
|
| |
enables SelectionDAG::getLoad at MipsISelLowering.cpp:1914 to return a
pre-existing node instead of redundantly create a new node every time it is
called.
llvm-svn: 133811
|
| |
|
|
| |
llvm-svn: 133810
|
| |
|
|
| |
llvm-svn: 133809
|
| |
|
|
|
|
| |
rdar://9667872
llvm-svn: 133808
|
| |
|
|
| |
llvm-svn: 133807
|
| |
|
|
|
|
| |
objects. // rdar://9495837
llvm-svn: 133806
|
| |
|
|
| |
llvm-svn: 133805
|