PR tree-optimization/88531
* gcc.target/i386/pr88531-1a.c: New test.
* gcc.target/i386/pr88531-1b.c: Likewise.
* gcc.target/i386/pr88531-1c.c: Likewise.
* gcc.target/i386/pr88531-2a.c: Likewise.
* gcc.target/i386/pr88531-2b.c: Likewise.
* gcc.
Update vector_all_ones_operand to return true for const all 1s float
vectors.
gcc/
PR target/101804
* config/i386/predicates.md (vector_all_ones_operand): Return
true for const all 1s float vectors.
gcc/testsuite/
PR target/101804
* gcc.target/i386/avx2-g
The KIND argument of the INDEX intrinsic is a compile time constant
that is used at compile time only to resolve to a kind-specific library
method. It is otherwise completely ignored at runtime, and there is
no code generated for it as the library procedure has no kind argument.
This confuses the
Hello,
This is a variant of the patch series previously posted for master at [1],
without patches 1 to 5.
It has a more limited impact, which makes it more suitable for the release
branches.
The problematic case is intrinsic procedures where an argument is actually not
used in the code generat
This reverts commit d09847357b965a2c2cda063827ce362d4c9c86f2 except for
its testcase.
gcc/fortran/
* intrinsic.c (add_sym_4ind): Remove.
(add_functions): Use add_sym4 instead of add_sym4ind.
Don’t special case the index intrinsic.
* iresolve.c (gfc_resolve_index_fu
On Mon, Aug 2, 2021 at 3:23 PM Ian Lance Taylor wrote:
>
> The upcoming Go 1.17 release adds two new functions to the unsafe
> package: unsafe.Add and unsafe.Slice. These functions must be
> implemented in the compiler. This patch implements them for gccgo.
> Bootstrapped and ran Go testsuite on
On 8/6/2021 11:24 PM, Jeff Law wrote:
On 8/6/2021 2:59 PM, sunil.k.pandey via Gcc-patches wrote:
On Linux/x86_64,
f31da42e047e8018ca6ad9809273bc7efb6ffcaf is the first bad commit
commit f31da42e047e8018ca6ad9809273bc7efb6ffcaf
Author: Richard Biener
Date: Fri Aug 6 14:39:05 2021 +0200
A simulator can easily spend more than 10 minutes running this
test-case, and the default timeout is at 5 minutes. Better allow
even slower machines; use 4 as the factor.
Regarding relative runtime numbers (very local; mmixware simulator for
mmix-knuth-mmixware): test01 and test05 finish momentari
On Sun, 8 Aug 2021, 03:42 Hans-Peter Nilsson, wrote:
> A simulator can easily spend more than 10 minutes running this
> test-case, and the default timeout is at 5 minutes. Better allow
> even slower machines; use 4 as the factor.
>
> Regarding relative runtime numbers (very local; mmixware simula
