http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52614

             Bug #: 52614
           Summary: [4.8 Regression] Test failures in gcc.dg/vect:
                    vectorizing unaligned access
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassig...@gcc.gnu.org
        ReportedBy: domi...@lps.ens.fr
                CC: greta.yo...@arm.com, ia...@gcc.gnu.org,
                    rgue...@gcc.gnu.org
            Target: arm*-*-* ppc*-*-* ia64-*-*


AFAICT pr52603 is not fixed after revision 185474 (see
http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02065.html ). In addition
similar errors occur on ppc*-*-* and ia64-*-* (see
http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02068.html ,
http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02104.html , and
http://gcc.gnu.org/ml/gcc-testresults/2012-03/msg02063.html ).

On powerpc-apple-darwin9, the tests pass with the following patch

--- ../../_gcc_clean/gcc/testsuite/gcc.dg/vect/vect.exp    2011-11-10
13:08:06.000000000 +0100
+++ ../../work/gcc/testsuite/gcc.dg/vect/vect.exp    2012-03-19
10:47:12.000000000 +0100
@@ -40,7 +40,7 @@ if ![check_vect_support_and_set_flags] {
 }

 # These flags are used for all targets.
-lappend DEFAULT_VECTCFLAGS "-ftree-vectorize" "-fno-vect-cost-model"
+lappend DEFAULT_VECTCFLAGS "-ftree-vectorize" "-fno-vect-cost-model"
"-fno-common"

 # Initialize `dg'.
 dg-init

        === gcc Summary for unix/-m64 ===

# of expected passes        3709
# of expected failures        127
# of unsupported tests        37

        === gcc Summary ===

# of expected passes        7443
# of expected failures        241
# of unsupported tests        64

I don't know if this related, but the failures reported in pr52491 disappeared
between revisions 185328 and 185486. Also on x86_64-apple-darwin10, the
polyhedron test gas_dyn.f90 runs 10% faster after revision 185454 than for
revision 185095.

Reply via email to