This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: optimization/8599: [3.2 regression] loop unroll bug with -march=k6-3
> Well, Dale's patch1 is already checked in, this was the regression causing
> one. If that's what you mean, yes, that's what I meant too :-).
Not exactly, I was considering the patches in chronological order. Here's the
lexicon:
- rth's patch: the backported patch from rth you posted,
- dale's patch1: the backported patch from Dale I posted,
- dale's patch2: the backported patch already checked in,
> My bootstraps on powerpc-linux-gnu and i686-linux-gnu with this setup
> completed without regressions.
gcc 3.2.1: 5 failures
FAIL: g77.f-torture/execute/intrinsic-unix-bessel.f execution, -O0
FAIL: g77.f-torture/execute/intrinsic-unix-bessel.f execution, -O1
FAIL: g77.f-torture/execute/intrinsic-unix-bessel.f execution, -O2
FAIL: g77.f-torture/execute/intrinsic-unix-bessel.f execution, -O3 -g
FAIL gcc.dg/i386-unroll-1.c
gcc 3.2.1 + rth's patch: 1 failure
FAIL: g77.f-torture/execute/intrinsic-unix-bessel.f execution, -O0
gcc 3.2.1 + rth's patch + Dale's patch1: 1 failure
FAIL: g77.f-torture/execute/intrinsic-unix-bessel.f execution, -O0
gcc 3.2.1 + rth's patch + Dale's patch1 + Dale's patch2: 2 failures
FAIL: g77.f-torture/execute/intrinsic-unix-bessel.f execution, -O0
FAIL: g77.f-torture/execute/intrinsic-unix-bessel.f execution, -O2
However the failures of g77.f-torture/execute/intrinsic-unix-bessel.f are NOT
reproducible: sometimes the execution is ok, sometimes it is not. And this
happens with mainline too on i586 (except at -Os).
--
Eric Botcazou