| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
| |
llvm-svn: 142341
|
| |
|
|
| |
llvm-svn: 142338
|
| |
|
|
|
|
| |
rdar://10288916
llvm-svn: 142337
|
| |
|
|
| |
llvm-svn: 142336
|
| |
|
|
| |
llvm-svn: 142332
|
| |
|
|
| |
llvm-svn: 142323
|
| |
|
|
| |
llvm-svn: 142321
|
| |
|
|
|
|
|
|
| |
appropriate CMake dependencies.
Thanks to Raphael Espindola for tracking down the CMake issues.
llvm-svn: 142306
|
| |
|
|
| |
llvm-svn: 142303
|
| |
|
|
|
|
|
|
|
|
| |
.file filenumber "directory" "filename"
This removes one join+split of the directory+filename in MC internals. Because
bitcode files have independent fields for directory and filenames in debug info,
this patch may change the .o files written by existing .bc files.
llvm-svn: 142300
|
| |
|
|
| |
llvm-svn: 142299
|
| |
|
|
| |
llvm-svn: 142297
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Linking CXX executable ../../bin/llvm-as
../../lib/libLLVMAsmParser.a(LLParser.cpp.o):/home/espindola/llvm/llvm/lib/AsmParser/LLParser.cpp:function llvm::LLParser::ParseTargetDefinition(): error: undefined reference to 'llvm::TargetData::parseSpecifier(llvm::StringRef, llvm::TargetData*)'
clang-3: error: linker command failed with exit code 1 (use -v to see invocation)
Revert "Validate target data layout strings."
This reverts commit 599d2d4c25d3aee63a21d9c67a88cd43bd971b7e.
llvm-svn: 142296
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use the custom inserter for the ARM setjmp intrinsics. Instead of creating the
SjLj dispatch table in IR, where it frequently violates serveral assumptions --
in particular assumptions made by the landingpad instruction about what can
branch to a landing pad and what cannot. Performing this in the back-end allows
us to violate these assumptions without the IR getting angry at us.
It also allows us to perform a small optimization. We can shove the address of
the dispatch's basic block into the function context and not have to add code
around the setjmp to check for the return value and jump to the dispatch.
Neat, huh?
<rdar://problem/10116753>
llvm-svn: 142294
|
| |
|
|
|
|
|
|
| |
NEON immediates are "interesting". Start of the work to handle parsing them
in an 'as' compatible manner. Getting the matcher to play nicely with
these and the floating point immediates from VFP is an extra fun wrinkle.
llvm-svn: 142293
|
| |
|
|
|
|
| |
Invalid strings in asm files will result in parse errors. Invalid string literals passed to TargetData constructors will result in an assertion.
llvm-svn: 142288
|
| |
|
|
| |
llvm-svn: 142259
|
| |
|
|
|
|
| |
pass renumbers the blocks again.
llvm-svn: 142258
|
| |
|
|
|
|
| |
lowered to. This fixes a lot of verifier failures on the test suite.
llvm-svn: 142254
|
| |
|
|
| |
llvm-svn: 142248
|
| |
|
|
|
|
|
| |
Once the intrinsics are marked as having a custom inserter, it will call this
method to emit the dispatch table into the machine function.
llvm-svn: 142245
|
| |
|
|
| |
llvm-svn: 142239
|
| |
|
|
|
|
|
| |
expanding conditional moves, which is not needed since architectures that lack
support for conditional moves have been removed.
llvm-svn: 142226
|
| |
|
|
| |
llvm-svn: 142224
|
| |
|
|
|
|
| |
Patch by Joe Abbey <jabbey@arxan.com>.
llvm-svn: 142223
|
| |
|
|
| |
llvm-svn: 142220
|
| |
|
|
| |
llvm-svn: 142217
|
| |
|
|
| |
llvm-svn: 142216
|
| |
|
|
| |
llvm-svn: 142214
|
| |
|
|
| |
llvm-svn: 142211
|
| |
|
|
|
|
| |
source registers and redefine 32-bit and 64-bit instructions.
llvm-svn: 142210
|
| |
|
|
| |
llvm-svn: 142209
|
| |
|
|
|
|
| |
and have 32-bit and 64-bit instructions derive from it.
llvm-svn: 142207
|
| |
|
|
| |
llvm-svn: 142205
|
| |
|
|
| |
llvm-svn: 142204
|
| |
|
|
|
|
| |
There is no reason to have simple IR level pass in lib/Target.
llvm-svn: 142200
|
| |
|
|
|
|
| |
to reflect this
llvm-svn: 142194
|
| |
|
|
|
|
| |
that cpuid leaf 7 can't be queried on versions of Visual Studio earlier than VS 2008 SP1. Fixes PR11147.
llvm-svn: 142177
|
| |
|
|
| |
llvm-svn: 142176
|
| |
|
|
| |
llvm-svn: 142171
|
| |
|
|
| |
llvm-svn: 142170
|
| |
|
|
| |
llvm-svn: 142141
|
| |
|
|
|
|
|
|
| |
<stdin>:1:12: error: register %rax is only available in 64-bit mode
incl %rax
^~~~
llvm-svn: 142137
|
| |
|
|
|
|
|
|
|
|
| |
print ranges for invalid operands.
<stdin>:1:4: error: invalid instruction mnemonic 'abc'
abc incl %edi
^~~
llvm-svn: 142135
|
| |
|
|
|
|
| |
no pattern.
llvm-svn: 142130
|
| |
|
|
| |
llvm-svn: 142122
|
| |
|
|
|
|
| |
VMREAD, and VMWRITE to remove hack from X86RecognizableInstr.
llvm-svn: 142117
|
| |
|
|
|
|
|
| |
These missing flags show up as errors when running -verify-coalescing on
test-suite.
llvm-svn: 142111
|
| |
|
|
| |
llvm-svn: 142110
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
does. Enhance
the X86 asmparser to produce ranges in the one case that was annoying me, for example:
test.s:10:15: error: invalid operand for instruction
movl 0(%rax), 0(%edx)
^~~~~~~
It should be straight-forward to enhance filecheck, tblgen, and/or the .ll parser to use
ranges where appropriate if someone is interested.
llvm-svn: 142106
|