On Wed, Oct 30, 2019 at 06:16:43PM +, Andre Vieira (lists) wrote:
> 2019-10-30 Andre Vieira
>
> * params.def (PARAM_VECT_EPILOGUES_NOMASK): Enable by default.
This broke quite a few tests in libgomp, and as they are execution failures,
just trying to work around it in the test is n
This patch seems to break
libgomp.fortran/examples-4/simd-3.f90
at run time as the calculated value is way off: "diff = sum - sum_ref"
is -12576 while abs(diff) < 1e-16 is the check.
It works with -O0 or without -mavx; (Hence, -Os or -O1 + -mavx cause the
fail.)
Please have a look.
Tobias
On October 30, 2019 7:16:43 PM GMT+01:00, "Andre Vieira (lists)"
wrote:
>Hi,
>
>In this patch I turn epilogue vectorization on by default for all
>targets. After some discussions I decided to take the following testing
>
>approach:
>
>1) I have disabled epilogue vectorization for all tests that
Hi,
In this patch I turn epilogue vectorization on by default for all
targets. After some discussions I decided to take the following testing
approach:
1) I have disabled epilogue vectorization for all tests that failed due
to scan-tree-dump failures inside:
- gcc.dg/vect
- gcc.target/i
On 8/23/19 10:50 AM, Andre Vieira (lists) wrote:
> I am not sure whether this is the right thing to do, we might want to
> enable this only for certain targets and if so, I also don't know how to
> tackle the testing issue where all the tests that check the number of
> times a dump mentions somethi
On Fri, 23 Aug 2019, Andre Vieira (lists) wrote:
> Hi,
>
> In this patch I turn epilogue vectorization on by default. I had to make
> changes to the tests since the vectorizer dumps now show the analysis for both
> the first and second vectorization. This required checks like
> 'scan-tree-dump-t
Hi,
In this patch I turn epilogue vectorization on by default. I had to
make changes to the tests since the vectorizer dumps now show the
analysis for both the first and second vectorization. This required
checks like 'scan-tree-dump-times' to be raised to meet the new numbers.
For some test
