| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
|
| |
The checks with the MARKER prefix were not being run over the right
input, because stderr was not redirected properly.
llvm-svn: 313596
|
| |
|
|
|
|
| |
Signed-off-by: Yonghong Song <yhs@fb.com>
Acked-by: Alexei Starovoitov <ast@kernel.org>
llvm-svn: 313593
|
| |
|
|
|
|
| |
Differential Revision: https://reviews.llvm.org/D37993
llvm-svn: 313592
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DBG_VALUEs"
This caused asserts in Chromium. See http://crbug.com/766261
> Summary:
> This comes up in optimized debug info for C++ programs that pass and
> return objects indirectly by address. In these programs,
> llvm.dbg.declare survives optimization, which causes us to emit indirect
> DBG_VALUE instructions. The fast register allocator knows to insert
> DW_OP_deref when spilling indirect DBG_VALUE instructions, but the
> LiveDebugVariables did not until this change.
>
> This fixes part of PR34513. I need to look into why this doesn't work at
> -O0 and I'll send follow up patches to handle that.
>
> Reviewers: aprantl, dblaikie, probinson
>
> Subscribers: qcolombet, hiraditya, llvm-commits
>
> Differential Revision: https://reviews.llvm.org/D37911
llvm-svn: 313589
|
| |
|
|
|
|
|
| |
NFC intended here, this only updates clang and lld's lit configs
to use some helper functionality in the lit.llvm submodule.
llvm-svn: 313579
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If we have an AssertZext of a truncated value that has already been AssertZext'ed,
we can assert on the wider source op to improve the zext-y knowledge:
assert (trunc (assert X, i8) to iN), i1 --> trunc (assert X, i1) to iN
This moves a fold from being Mips-specific to general combining, and x86 shows
improvements.
Differential Revision: https://reviews.llvm.org/D37017
llvm-svn: 313577
|
| |
|
|
|
|
|
| |
The code responsible for these transforms has the potential to add 2
instructions and break min/max patterns (PR33301).
llvm-svn: 313575
|
| |
|
|
| |
llvm-svn: 313567
|
| |
|
|
| |
llvm-svn: 313566
|
| |
|
|
|
|
| |
Differential Revision: https://reviews.llvm.org/D37981
llvm-svn: 313565
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rL310710 allowed store merging to occur after legalization to catch stores that are created late,
but this exposes a logic hole seen in PR34217:
https://bugs.llvm.org/show_bug.cgi?id=34217
We will miss merging stores if the target lowers vector extracts into target-specific operations.
This patch allows store merging to occur both before and after legalization if the target chooses
to get maximum merging.
I don't think the potential regressions in the other tests are relevant. The tests are for
correctness of weird IR constructs rather than perf tests, and I think those are still correct.
Differential Revision: https://reviews.llvm.org/D37987
llvm-svn: 313564
|
| |
|
|
|
|
|
|
|
|
|
|
| |
zext is AssertZext
The AssertZext we might see in this case is only giving information about the lower 32 bits. It isn't providing information about the upper 32 bits. So we should emit a zext.
This fixes PR28540.
Differential Revision: https://reviews.llvm.org/D37729
llvm-svn: 313563
|
| |
|
|
| |
llvm-svn: 313559
|
| |
|
|
| |
llvm-svn: 313548
|
| |
|
|
|
|
|
|
| |
results.
As commented on D37849, AVX1 targets were missing a chance to use vmovmskps for v8f32/v8i32 results for bool vector bitcasts
llvm-svn: 313547
|
| |
|
|
| |
llvm-svn: 313545
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Add test cases when float <-> pointer types conversion is triggered
in presence of load instructions.
Reviewers: Ayal, srhines, mkuper, rengolin
Reviewed By: rengolin
Subscribers: javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D37967
llvm-svn: 313544
|
| |
|
|
|
|
|
|
|
|
|
|
| |
bits.
For cases where we are BITCASTing to vectors of smaller elements, then if the entire source was a splatted sign (src's NumSignBits == SrcBitWidth) we can say that the dst's NumSignBit == DstBitWidth, as we're just splitting those sign bits across multiple elements.
We could generalize this but at the moment the only use case I have is to peek through bitcasts to vector comparison results.
Differential Revision: https://reviews.llvm.org/D37849
llvm-svn: 313543
|
| |
|
|
|
|
|
|
|
|
|
|
| |
enabled
The shuffle combining and lowerVectorShuffleAsLanePermuteAndBlend were both still trying to use VPERM2XF128 for unary shuffles when AVX2 is enabled. VPERM2X128 takes two inputs meaning when we use it for a unary shuffle one of those inputs is left undefined creating a false dependency on whatever register gets allocated there.
If we have VPERMQ/PD we should prefer those since they only have a single input.
Differential Revision: https://reviews.llvm.org/D37947
llvm-svn: 313542
|
| |
|
|
|
|
|
|
|
|
| |
Add the missing hardware features the ProcA55 and ProcA75 feature.
These are already enabled via the target parser, but I had missed
them in the backend.
Differential Revision: https://reviews.llvm.org/D37974
llvm-svn: 313535
|
| |
|
|
|
|
|
|
|
|
| |
Implement the isTruncateFree hooks, lifted from AArch64, that are
used by TargetTransformInfo. This allows simplifycfg to reduce the
test case into a single basic block.
Differential Revision: https://reviews.llvm.org/D37516
llvm-svn: 313533
|
| |
|
|
|
|
|
|
| |
As discussed on PR28925 and D37849.
Differential Revision: https://reviews.llvm.org/D37975
llvm-svn: 313532
|
| |
|
|
|
|
|
|
|
|
|
| |
The indexed dot product instructions only accept the lower 16 D-registers as
the indexed register, but we were e.g. incorrectly accepting:
vudot.u8 d16,d16,d18[0]
Differential Revision: https://reviews.llvm.org/D37968
llvm-svn: 313531
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch makes the `.eh_frame` extension an alias for `.debug_frame`.
Up till now it was only possible to dump the section using objdump, but
not with dwarfdump. Since the two are essentially interchangeable, we
dump whichever of the two is present.
As a workaround, this patch also adds parsing for 3 currently
unimplemented CFA instructions: `DW_CFA_def_cfa_expression`,
`DW_CFA_expression`, and `DW_CFA_val_expression`. Because I lack the
required knowledge, I just parse the fields without actually creating
the instructions.
Finally, this also fixes the typo in the `.debug_frame` section name
which incorrectly contained a trailing `s`.
Differential revision: https://reviews.llvm.org/D37852
llvm-svn: 313530
|
| |
|
|
| |
llvm-svn: 313529
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Subregister liveness tracking is not implemented for X86 backend, so
sometimes the whole super register is said to be live, when only a
subregister is really live. That might happen if the def and the use
are located in different MBBs, see added fixup-bw-isnt.mir test.
However, using knowledge of the specific instructions handled by the
bw-fixup-pass we can get more precise liveness information which this
change does.
Reviewers: MatzeB, DavidKreitzer, ab, andrew.w.kaylor, craig.topper
Reviewed By: craig.topper
Subscribers: n.bozhenov, myatsina, llvm-commits, hiraditya
Patch by Andrei Elovikov <andrei.elovikov@intel.com>
Differential Revision: https://reviews.llvm.org/D37559
llvm-svn: 313524
|
| |
|
|
|
|
|
|
|
| |
related to patch: https://reviews.llvm.org/D35772
adding llvm gathers test before gathers codegen support.
Differential Revision: https://reviews.llvm.org/D37800
llvm-svn: 313516
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
This change adds support for explicit tail-exit records to be written by
the XRay runtime. This lets us differentiate the tail exit
records/events in the log, and allows us to treat those exit events
especially in the future. For now we allow printing those out in YAML
(and reading them in).
Reviewers: kpw, pelikan
Subscribers: llvm-commits
Differential Revision: https://reviews.llvm.org/D37964
llvm-svn: 313514
|
| |
|
|
|
|
|
|
| |
unpcklpd for the packed single domain.
MOVLHPS has a smaller encoding than UNPCKLPD in the legacy encodings. With VEX and EVEX encodings it doesn't matter.
llvm-svn: 313509
|
| |
|
|
|
|
| |
instructions.
llvm-svn: 313508
|
| |
|
|
| |
llvm-svn: 313507
|
| |
|
|
|
|
| |
shuffles with SSE1 only.
llvm-svn: 313504
|
| |
|
|
|
|
| |
These can be implemented with movlhps and movhlps.
llvm-svn: 313503
|
| |
|
|
|
|
| |
Differential Revision: https://reviews.llvm.org/D37962
llvm-svn: 313490
|
| |
|
|
|
|
|
|
|
| |
This Disassembly support allows for 'round-trip' testing, and rv32i-valid.s
has been updated appropriately.
Differential Revision: https://reviews.llvm.org/D23567
llvm-svn: 313486
|
| |
|
|
|
|
|
|
|
|
| |
This patch supports all RV32I instructions as described in the RISC-V manual.
A future patch will add support for pseudoinstructions and other instruction
expansions (e.g. 0-arg fence -> fence iorw, iorw).
Differential Revision: https://reviews.llvm.org/D23566
llvm-svn: 313485
|
| |
|
|
| |
llvm-svn: 313483
|
| |
|
|
| |
llvm-svn: 313479
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: G_FCONSTANT support, port the implementation from X86FastIsel.
Reviewers: zvi, delena, guyblank
Reviewed By: delena
Subscribers: rovka, llvm-commits, kristof.beyls
Differential Revision: https://reviews.llvm.org/D37734
llvm-svn: 313478
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was a bug in the test that was only exposed as a result of
refactoring some code in lit configuration files. Previously,
llvm's lit configuration would only set the target-windows feature
if the system was also windows. Since cross-compilation is
a thing, this isn't correct. target-windows should be set
independently of system-windows.
Adding to that bug, this particular test then checked for
target-windows when it really meant "can I call a certain API on
the host machine", which is what system-windows is for.
Ultimately, this test only works if *both* the target and host
are Windows, so I've updated the test to reflect that.
llvm-svn: 313468
|
| |
|
|
|
|
|
|
| |
There were some issues surrounding Py2 / Py3 compatibility, but
I've now tested with both Py2 and Py3 and everything seems to
work.
llvm-svn: 313467
|
| |
|
|
|
|
|
| |
This will print all children of a DIE when selectively printing only
one DIE at a given offset.
llvm-svn: 313464
|
| |
|
|
| |
llvm-svn: 313463
|
| |
|
|
|
|
|
|
|
|
|
|
| |
COMDAT groups at once.
readelf tool reports an error when output contains the same section
in multiple COMDAT groups. That can be useful.
Path teaches llvm-readobj to do the same.
Differential revision: https://reviews.llvm.org/D37567
llvm-svn: 313459
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows vector-sized store merging of constants in DAGCombiner using the existing code in MergeConsecutiveStores().
All of the twisted logic that decides exactly what vector operations are legal and fast for each particular CPU are
handled separately in there using the appropriate hooks.
For the motivating tests in merge-store-constants.ll, we already produce the same vector code in IR via the SLP vectorizer.
So this is just providing a backend backstop for code that doesn't go through that pass (-O1). More details in PR24449:
https://bugs.llvm.org/show_bug.cgi?id=24449 (this change should be the last step to resolve that bug)
Differential Revision: https://reviews.llvm.org/D37451
llvm-svn: 313458
|
| |
|
|
|
|
|
|
|
|
| |
the load is on the first input to the SDNode.
We just need to toggle bits 1 and 5 of the immediate and swap the sources. The peephole pass could trigger commuting/folding for this later, but its easy enough to fix in isel.
Disable the peephole pass on the main vperm2x128 test so we know we're doing this through isel.
llvm-svn: 313455
|
| |
|
|
|
|
| |
the instrinsic upgrade file and regenerated.
llvm-svn: 313454
|
| |
|
|
|
|
| |
I missed the we already had a pretty thorough test file for these instructions.
llvm-svn: 313451
|
| |
|
|
|
|
|
|
| |
shuffles.
I've moved the test cases from the InstCombine optimizations to the backend to keep the coverage we had there. It covered every possible immediate so I've preserved the resulting shuffle mask for each of those immediates.
llvm-svn: 313450
|
| |
|
|
|
|
| |
Assume they were moved during autoupgrading and not changed.
llvm-svn: 313448
|