- Apr 11, 2023
-
-
Congcong Cai authored
Reviewed By: aheejin Differential Revision: https://reviews.llvm.org/D147884
-
Nicolas Vasilache authored
-
Simon Pilgrim authored
[X86] Remove unnecessary OneUse limit from combineToExtendBoolVectorInReg (vXi1 bitcast(iX Cond)) select expansion We already allow multiple uses when calling from combineSext/combineZext - adding hasOneUse seems to have been a copy+paste from some of the similar AVX512 vselect folds. Fixes #62014
-
Amaury Séchet authored
-
Amaury Séchet authored
-
Felipe de Azevedo Piovezan authored
I've found that a frequent source of debug information loss in optimized code is due to DEBUG_VALUE intrinsics in a position of the instruction stream that is outside the scope of the variable it describes. Tracking these is pretty difficult with the existing debug messages of the history calculator; this patch addresses the issue by making it obvious when this event happens. Differential Revision: https://reviews.llvm.org/D147718
-
skc7 authored
-
Guillaume Chatelet authored
This is ok as we build the libraries with `-ffreestanding` which implies `-fno-builtin` on all functions.
-
Nico Weber authored
This reverts commit 070233da. It also reverts follow-ups 2588e831 and 027f60a6.
-
Guillaume Chatelet authored
-
Sjoerd Meijer authored
Fixed two test cases that relied on Asserts, and added a fallthrough annotation to the switch case.
-
Igor Kirillov authored
Differential Revision: https://reviews.llvm.org/D147659
-
Amaury Séchet authored
This limitation was discovered thanks to some regression in D127115 . Reviewed By: RKSimon Differential Revision: https://reviews.llvm.org/D147821
-
Simon Pilgrim authored
Ensure we test different vector element sizes
-
Simon Pilgrim authored
vector-bo-select.ll should only be used for binop identity select tests
-
Nikita Popov authored
These methods can be called with an O0 level nowadays.
-
Guillaume Chatelet authored
-
Martin Braenne authored
Reviewed By: gribozavr2 Differential Revision: https://reviews.llvm.org/D148004
-
Nikita Popov authored
In the non-ThinLTO pipeline this was directly before PipelineStartEP, in the ThinLTO pipeline it was directly after. I don't think the specific position matters here, just make sure it's the same for both pipelines.
-
Nikita Popov authored
-
Nikita Popov authored
buildModuleSimplificationPipeline() is not used for O0.
-
Matt Arsenault authored
The math libraries have a lot of code that performs manual sign bit operations by bitcasting doubles to int2 and doing bithacking on them. This is a bad canonical form we should rewrite to use high level sign operations directly on double. To avoid codegen regressions, we need to do a better job moving fnegs to operate only on the high 32-bits. This is only halfway to fixing the real case.
-
Simon Pilgrim authored
Added multiuse checks for v8i16 and v8f32 cases
-
Alex Zinenko authored
-
Alex Zinenko authored
Ops from the Math dialect use fastmath attributes defined in Arith. Therefore Math dialect must declare a dependency on Arith for proper construction and parsing. Reviewed By: tpopp Differential Revision: https://reviews.llvm.org/D147999
-
Simon Pilgrim authored
-
Max Kazantsev authored
Avoid divergence b/w different kinds of hoisting with reassociation. Make them all collect general stat NumHoisted and also specific stats for each particular transform.
-
Momchil Velikov authored
Reviewed By: MatzeB Differential Revision: https://reviews.llvm.org/D145707
-
Max Kazantsev authored
They all are now handled by hoistArithmetics, and only it should be forwarded.
-
Max Kazantsev authored
Should not optimize here because no-overflow is not proved.
-
Nikita Popov authored
In this case the source GEP might not be hoisted even though it has invariant operands. For now just bail out, but we might need additional checks for AllowSpeculation in these special-case reassociation folds.
-
Alexis Engelke authored
Depends on D145791 Storing instruction bytes directly in a SmallVector instead of a raw_ostream yields better encoding performance (in some applications, the improvment is ~1% of the complete back-end time). Reviewed By: MaskRay, Amir Differential Revision: https://reviews.llvm.org/D145792
-
Alexis Engelke authored
The type of a function is nowadays just an opaque pointer, which is not helpful when analyzing FastISel misses. Instead print the actual function type of the function. Reviewed By: efriedma Differential Revision: https://reviews.llvm.org/D147716
-
Jon Chesterfield authored
-
David Spickett authored
This used to say: For example, clang --target=aarch64-unknown-linux-gui -mcpu=cortex-a35 Which works but I think it was meant to be `-gnu` not `-gui`. From my AArch64 Linux build: ``` $ ./bin/clang --version clang version 17.0.0 <...> Target: aarch64-unknown-linux-gnu ``` Originally added in af857b93.
-
Sjoerd Meijer authored
This reverts commit d0027e0b. Need to look at 2 test failures.
-
Diana Picus authored
The GFX11 NGG Streamout Instructions perform atomic operations on dedicated registers. At the moment, they lack machine memory operands, which causes the si-memory-legalizer pass to treat them conservatively and introduce several unnecessary waits and cache invalidations. This patch introduces a new address space to represent these special registers and teaches instruction selection to add memory operands with this new address space to DS_ADD/SUB_GS_REG_RTN. Since this address space is meant to be compiler-internal, we move it up a bit from the other address spaces and give it the number 128. According to the LLVM Language Reference, address space numbers can go all the way up to 2^24, but I'm not sure how well this is supported in practice [1], so using a smaller number seems safer. [1] https://github.com/llvm/llvm-project/blob/0107513fe79da7670e37c29c0862794a2213a89c/llvm/utils/TableGen/IntrinsicEmitter.cpp#L401 Differential Revision: https://reviews.llvm.org/D146031
-
Diana Picus authored
-
Heejin Ahn authored
When we encounter an `else`, `catch`, or `catch_all`, we currently just push the structure `NestingType` and don't preserve the original `if` and `try`'s signature. So after we pass `else`/`catch`/`catch_all`, we can't check if the values on stack have the correct types when we encounter `end_if` or `end_try`. This CL fixes the issue, and modifies the existing test to be correct (some of them had `try` without `catch`). Reviewed By: dschuff Differential Revision: https://reviews.llvm.org/D147881
-
Heejin Ahn authored
We disable type check in unreachable code, but when the unreachable code is enclosed within a block-like structure, the block as a whole has a valid type and we should continue type checking after the block. But it looks we currently only do that for blocks and not other block-like structures (`loop`s, `try`s, and `if`s). Also unreachable code within `if`'s true body shouldn't disable type checking in `else` body, and that in `try` body shouldn't disable type checking in `catch/catch_all` body. This also causes the values/types on the stack to be correctly checked when encounterint `catch`, `catch_all`, and `delegate`. Reviewed By: dschuff Differential Revision: https://reviews.llvm.org/D147852
-