This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug testsuite/40359] [4.5 Regression] Revision 148211 caused a lot of failures in the vect test suite.



------- Comment #24 from dominiq at lps dot ens dot fr  2009-06-17 10:17 -------
(In reply to comment #23)
If I add to vect-42.c (with my patch) the line

/* { dg-final { scan-tree-dump-times "bla bla bla" 1 "vect" { target
vector_alignment_reachable } } } */

I get:

Running target unix
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using /opt/gcc/gcc-4.5-work/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /opt/gcc/gcc-4.5-work/gcc/testsuite/gcc.dg/vect/vect.exp ...
FAIL: gcc.dg/vect/vect-42.c scan-tree-dump-times vect "bla bla bla" 1

                === gcc Summary for unix ===

# of expected passes            5
# of unexpected failures        1
Running target unix/-m64
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using /opt/gcc/gcc-4.5-work/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /opt/gcc/gcc-4.5-work/gcc/testsuite/gcc.dg/vect/vect.exp ...

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

# of expected passes            3
# of expected failures          2

i.e., the test is done for -m32 (and fail) but not for -m64.

If I add the line

* { dg-final { scan-tree-dump-times "bla bla bla" 1 "vect" { target { !
vect_hw_misalign } } } } *//

I get

Running target unix
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using /opt/gcc/gcc-4.5-work/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /opt/gcc/gcc-4.5-work/gcc/testsuite/gcc.dg/vect/vect.exp ...
FAIL: gcc.dg/vect/vect-42.c scan-tree-dump-times vect "bla bla bla" 1

                === gcc Summary for unix ===

# of expected passes            5
# of unexpected failures        1
Running target unix/-m64
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using /opt/gcc/gcc-4.5-work/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /opt/gcc/gcc-4.5-work/gcc/testsuite/gcc.dg/vect/vect.exp ...
FAIL: gcc.dg/vect/vect-42.c scan-tree-dump-times vect "bla bla bla" 1

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

# of expected passes            3
# of unexpected failures        1
# of expected failures          2

i.e., vect_hw_misalign is false for both -m32 and -m64.

So it looks that vect_hw_misalign has the opposite meaning of that assumed in
comment #16:

> hmmm... versioning should not be done for targets that support
> vect_hw_misalign... 

Final note, the change in comment #17 does not help.


-- 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]