- Jul 28, 2011
-
-
Kevin Enderby authored
llvm-mc gives an "invalid operand" error for instructions that take an unsigned immediate which have the high bit set such as: pblendw $0xc5, %xmm2, %xmm1 llvm-mc treats all x86 immediates as signed values and range checks them. A small number of x86 instructions use the imm8 field as a set of bits. This change only changes those instructions and where the high bit is not ignored. The others remain unchanged. llvm-svn: 136287
-
Eli Friedman authored
llvm-svn: 136283
-
- Jul 27, 2011
-
-
Eli Friedman authored
X86ISD::MEMBARRIER does not require SSE2; it doesn't actually generate any code, and all x86 processors will honor the required semantics. llvm-svn: 136249
-
Jeffrey Yasskin authored
C++0x. llvm-svn: 136211
-
Bruno Cardoso Lopes authored
llvm-svn: 136201
-
Bruno Cardoso Lopes authored
usage of the shuffle bitmask. Both work in 128-bit lanes without crossing, but in the former the mask of the high part is the same used by the low part while in the later both lanes have independent masks. Handle this properly and and add support for vpermilpd. llvm-svn: 136200
-
Bruno Cardoso Lopes authored
llvm-svn: 136199
-
Evan Cheng authored
llvm-svn: 136197
-
Benjamin Kramer authored
On x86 we can't encode an immediate LHS of a sub directly. If the RHS comes from a XOR with a constant we can fold the negation into the xor and add one to the immediate of the sub. Then we can turn the sub into an add, which can be commuted and encoded efficiently. This code is generated for __builtin_clz and friends. llvm-svn: 136167
-
Bruno Cardoso Lopes authored
different from the previous 128-bit because they work in lanes. Update a few comments and add testcases llvm-svn: 136157
-
- Jul 26, 2011
-
-
Eli Friedman authored
Prevent x86-specific DAGCombine from creating nodes with illegal type (which could not be selected). Fixes a minor isel issue that was breaking the testcase from r136130. llvm-svn: 136148
-
Bruno Cardoso Lopes authored
llvm-svn: 136109
-
Bruno Cardoso Lopes authored
llvm-svn: 136108
-
Bill Wendling authored
llvm-svn: 136065
-
Bruno Cardoso Lopes authored
llvm-svn: 136051
-
Bruno Cardoso Lopes authored
support for 256-bit versions (but no instruction selection yet, coming next). llvm-svn: 136050
-
Bruno Cardoso Lopes authored
llvm-svn: 136049
-
Bruno Cardoso Lopes authored
llvm-svn: 136048
-
Bruno Cardoso Lopes authored
27 insertions(+), 62 deletions(-) llvm-svn: 136047
-
Evan Cheng authored
llvm-svn: 136031
-
Evan Cheng authored
Rename TargetAsmParser to MCTargetAsmParser and TargetAsmLexer to MCTargetAsmLexer; rename createAsmLexer to createMCAsmLexer and createAsmParser to createMCAsmParser. llvm-svn: 136027
-
Chandler Carruth authored
The first problem to fix is to stop creating synthetic *Table_gen targets next to all of the LLVM libraries. These had no real effect as CMake specifies that add_custom_command(OUTPUT ...) directives (what the 'tablegen(...)' stuff expands to) are implicitly added as dependencies to all the rules in that CMakeLists.txt. These synthetic rules started to cause problems as we started more and more heavily using tablegen files from *subdirectories* of the one where they were generated. Within those directories, the set of tablegen outputs was still available and so these synthetic rules added them as dependencies of those subdirectories. However, they were no longer properly associated with the custom command to generate them. Most of the time this "just worked" because something would get to the parent directory first, and run tablegen there. Once run, the files existed and the build proceeded happily. However, as more and more subdirectories have started using this, the probability of this failing to happen has increased. Recently with the MC refactorings, it became quite common for me when touching a large enough number of targets. To add insult to injury, several of the backends *tried* to fix this by adding explicit dependencies back to the parent directory's tablegen rules, but those dependencies didn't work as expected -- they weren't forming a linear chain, they were adding another thread in the race. This patch removes these synthetic rules completely, and adds a much simpler function to declare explicitly that a collection of tablegen'ed files are referenced by other libraries. From that, we can add explicit dependencies from the smaller libraries (such as every architectures Desc library) on this and correctly form a linear sequence. All of the backends are updated to use it, sometimes replacing the existing attempt at adding a dependency, sometimes adding a previously missing dependency edge. Please let me know if this causes any problems, but it fixes a rather persistent and problematic source of build flakiness on our end. llvm-svn: 136023
-
Evan Cheng authored
llvm-svn: 136010
-
Bruno Cardoso Lopes authored
This also fixes PR10452 llvm-svn: 136004
-
Bruno Cardoso Lopes authored
llvm-svn: 136003
-
Bruno Cardoso Lopes authored
shuffle before inserting on a 256-bit vector. - Add AVX versions of movd/movq instructions - Introduce a few COPY patterns to match insert_subvector instructions. This turns a trivial insert_subvector instruction into a register copy, coalescing the xmm into a ymm and avoid emiting on more instruction. llvm-svn: 136002
-
Bruno Cardoso Lopes authored
native 256-bit vector instruction to do scalar_to_vector. llvm-svn: 136001
-
Benjamin Kramer authored
llvm-svn: 135996
-
- Jul 25, 2011
-
-
Eli Friedman authored
Addresses PR10466, although the crash from that PR only triggers in cases where DAGCombine misses optimizing a shuffle. llvm-svn: 135980
-
Evan Cheng authored
llvm-svn: 135974
-
Evan Cheng authored
llvm-svn: 135963
-
Evan Cheng authored
llvm-svn: 135954
-
Bill Wendling authored
Update the comment. This feature is available only on Darwin at the moment. Though it's not Darwin-specific. llvm-svn: 135951
-
Oscar Fuentes authored
llvm-svn: 135949
-
Evan Cheng authored
llvm-svn: 135939
-
Evan Cheng authored
llvm-svn: 135930
-
Bill Wendling authored
llvm-svn: 135924
-
Bill Wendling authored
llvm-svn: 135923
-
Bill Wendling authored
unwind encoding for that function. This simply crawls through the prolog looking for machine instrs marked as "frame setup". It can calculate from these what the compact unwind should look like. This is currently disabled because of needed linker support. But initial tests look good. llvm-svn: 135922
-
- Jul 23, 2011
-
-
Evan Cheng authored
llvm-svn: 135833
-