Hi!
As mentioned in the PR, vect-simd-clone-1[678]{,f}.c tests FAIL on
x86_64-linux with -m64/-march=cascadelake or -m32/-march=cascadelake,
there are 3 matches for the calls rather than expected two.
As suggested by Richi, this patch changes those tests to use
--param vect-epilogues-nomask=0 such
On Tue, 21 Mar 2023, Jakub Jelinek wrote:
> Hi!
>
> As mentioned in the PR, vect-simd-clone-1[678]{,f}.c tests FAIL on
> x86_64-linux with -m64/-march=cascadelake or -m32/-march=cascadelake,
> there are 3 matches for the calls rather than expected two.
> As suggested by Richi, this patch changes
On 21/03/2023 12:14, Jakub Jelinek wrote:
Hi!
As mentioned in the PR, vect-simd-clone-1[678]{,f}.c tests FAIL on
x86_64-linux with -m64/-march=cascadelake or -m32/-march=cascadelake,
there are 3 matches for the calls rather than expected two.
As suggested by Richi, this patch changes those tests
--- Begin Message ---
On Tue, Mar 21, 2023 at 12:35:19PM +, Andrew Stubbs wrote:
> > @@ -82,8 +82,7 @@ main ()
> > /* Ensure the the in-branch simd clones are used on targets that support
> > them.
> > Some targets use another call for the epilogue loops. */
> > -/* { dg-final { scan-
