| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 186227
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
ARM paired GPR COPY was being lowered to two MOVr without CC. This
patch puts the CC back.
My test is a reduction of the case where I encountered the issue,
64-bit atomics use paired GPRs.
The issue only occurs with selectionDAG, FastISel doesn't encounter it
so I didn't bother calling it.
llvm-svn: 186226
|
| |
|
|
| |
llvm-svn: 186225
|
| |
|
|
|
|
|
|
| |
undef vector of the wrong type.
LGTM'd by Nick Lewycky on IRC.
llvm-svn: 186224
|
| |
|
|
| |
llvm-svn: 186222
|
| |
|
|
|
|
|
| |
Now that we have robust function attributes, don't use a command line option to
specify the stack protecto buffer size.
llvm-svn: 186217
|
| |
|
|
| |
llvm-svn: 186216
|
| |
|
|
|
|
| |
This is a reimplemntation of the patch originally in r186107.
llvm-svn: 186215
|
| |
|
|
| |
llvm-svn: 186214
|
| |
|
|
| |
llvm-svn: 186213
|
| |
|
|
| |
llvm-svn: 186212
|
| |
|
|
|
|
| |
r186196.
llvm-svn: 186209
|
| |
|
|
| |
llvm-svn: 186206
|
| |
|
|
| |
llvm-svn: 186202
|
| |
|
|
| |
llvm-svn: 186200
|
| |
|
|
| |
llvm-svn: 186198
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes two bugs is lib/Object that the use in llvm-ar found:
* In OS X created archives, the name can be padded with nulls. Strip them.
* In the constructor, remember the first non special member and use that in
begin_children. This makes sure we skip all special members, not just the
first one.
The change to llvm-ar itself consist of
* Using lib/Object for reading archives instead of ArchiveReader.cpp.
* Writing the modified archive directly, instead of creating an in memory
representation.
The old Archive library was way more general than what is needed, as can
be seen by the diffstat of this patch.
Having llvm-ar using lib/Object now opens the way for creating regular symbol
tables for both native objects and bitcode files so that we can use those
archives for LTO.
llvm-svn: 186197
|
| |
|
|
| |
llvm-svn: 186196
|
| |
|
|
| |
llvm-svn: 186192
|
| |
|
|
|
|
|
| |
I'm guessing the failure had something to do with the double precision
floating point constant used in the test.
llvm-svn: 186191
|
| |
|
|
|
|
| |
radar://14351991
llvm-svn: 186189
|
| |
|
|
|
|
|
|
|
|
| |
Fixes a 35% degradation compared to unvectorized code in
MiBench/automotive-susan and an equally serious regression on a private
image processing benchmark.
radar://14351991
llvm-svn: 186188
|
| |
|
|
|
|
|
|
|
|
|
| |
Address calculation for gather/scather in vectorized code can incur a
significant cost making vectorization unbeneficial. Add infrastructure to add
cost.
Tests and cost model for targets will be in follow-up commits.
radar://14351991
llvm-svn: 186187
|
| |
|
|
| |
llvm-svn: 186186
|
| |
|
|
| |
llvm-svn: 186184
|
| |
|
|
| |
llvm-svn: 186183
|
| |
|
|
|
|
|
| |
Patch by: Niels Ole Salscheider
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
llvm-svn: 186182
|
| |
|
|
|
|
|
| |
Patch by: Niels Ole Salscheider
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
llvm-svn: 186181
|
| |
|
|
|
|
|
| |
Patch by: Niels Ole Salscheider
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
llvm-svn: 186180
|
| |
|
|
|
|
|
| |
Patch by: Niels Ole Salscheider
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
llvm-svn: 186179
|
| |
|
|
|
|
|
| |
Patch by: Niels Ole Salscheider
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
llvm-svn: 186178
|
| |
|
|
|
|
|
| |
Patch by: Niels Ole Salscheider
Reviewed-by: Tom Stellard <thomas.stellard@amd.com>
llvm-svn: 186177
|
| |
|
|
| |
llvm-svn: 186176
|
| |
|
|
|
|
|
| |
This is a generic block implementation that works on more than machine blocks.
The C++ mode addition is a bonus due to the extra space provided.
llvm-svn: 186175
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In particular:
movsbw %al, %ax --> cbtw
movswl %ax, %eax --> cwtl
movslq %eax, %rax --> cltq
According to Intel's manual those have the same performance characteristics but
come with a smaller encoding.
llvm-svn: 186174
|
| |
|
|
| |
llvm-svn: 186170
|
| |
|
|
|
|
|
|
| |
possible
Patch by Andrea Di Biagio
llvm-svn: 186165
|
| |
|
|
| |
llvm-svn: 186163
|
| |
|
|
|
|
|
|
| |
CHECK-LABEL is meant to be used in place on CHECK on lines containing identifiers or other unique labels (they need not actually be labels in the source or output language, though.) This is used to break up the input stream into separate blocks delineated by CHECK-LABEL lines, each of which is checked independently. This greatly improves the accuracy of errors and fix-it hints in many cases, and allows for FileCheck to recover from errors in one block by continuing to subsequent blocks.
Some tests will be converted to use this new directive in forthcoming patches.
llvm-svn: 186162
|
| |
|
|
| |
llvm-svn: 186159
|
| |
|
|
|
|
| |
We can't inline it but we can still CSE calls to it.
llvm-svn: 186156
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
against a constant."
This reverts commit r186107. It didn't handle wrapping arithmetic in the
loop correctly and thus caused the following C program to count from
0 to UINT64_MAX instead of from 0 to 255 as intended:
#include <stdio.h>
int main() {
unsigned char first = 0, last = 255;
do { printf("%d\n", first); } while (first++ != last);
}
Full test case and instructions to reproduce with just the -indvars pass
sent to the original review thread rather than to r186107's commit.
llvm-svn: 186152
|
| |
|
|
|
|
| |
cases are added.
llvm-svn: 186151
|
| |
|
|
|
|
| |
Sigh, twice in two days sorry. One day I'll remember...
llvm-svn: 186150
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Normal (sext (setcc ...)) sequences are optimised into
(select_cc ..., -1, 0) by DAGCombiner::visitSIGN_EXTEND.
However, this is deliberately not done for vectors, and after
vector type legalization we have (sext_inreg (setcc ...)) instead.
I wondered about trying to extend DAGCombiner to handle this case too,
but it seemed to be a loss on some other targets I tried, even those for
which SETCC isn't "legal" and SELECT_CC is.
llvm-svn: 186149
|
| |
|
|
|
|
|
|
|
|
|
|
| |
GPR and FPR constraints like "{r2}" and "{f2}" weren't handled correctly
because the name-to-regno mapping depends on the value type and
(because of that) the internal names in RegStrings are not the
same as the AsmName.
CC constraints like "{cc}" didn't work either because there was no
associated register class.
llvm-svn: 186148
|
| |
|
|
|
|
|
| |
If the source of these instructions is spilled we should load the destination.
If the destination is spilled we should store the source.
llvm-svn: 186147
|
| |
|
|
|
|
| |
Thank Nick for figuring out these problems.
llvm-svn: 186146
|
| |
|
|
| |
llvm-svn: 186145
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
This patch adds explicit calling convention types for the Win64 and
System V/x86-64 ABIs. This allows code to override the default, and use
the Win64 convention on a target that wants to use SysV (and
vice-versa). This is needed to implement the `ms_abi` and `sysv_abi` GNU
attributes.
Reviewers:
CC:
llvm-svn: 186144
|