This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/54427] Expose more vector extensions
- From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 20 Sep 2012 19:00:47 +0000
- Subject: [Bug c++/54427] Expose more vector extensions
- Auto-submitted: auto-generated
- References: <bug-54427-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54427
Pat Haugen <pthaugen at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pthaugen at gcc dot gnu.org
--- Comment #4 from Pat Haugen <pthaugen at gcc dot gnu.org> 2012-09-20 19:00:47 UTC ---
(In reply to comment #2)
> * gcc.c-torture/execute/vector-compare-2.c: Move ...
> * c-c++-common/torture/vector-compare-2.c: ... here.
This test is now failing on powerpc64-unknown-linux-gnu due to warning messages
being emitted for 32-bit.
FAIL: c-c++-common/torture/vector-compare-2.c -O0 (test for excess errors)
FAIL: c-c++-common/torture/vector-compare-2.c -O1 (test for excess errors)
...
This is due to the fact that in the old location the compile command included
-w which suppressed warnings, whereas the new location does not. The test can
be fixed for powerpc by adding the following line (as is present in
c-c++-common/vector-compare-2.c).
/* { dg-options "-mabi=altivec" { target { { powerpc*-*-linux* } && ilp32 } } }
*/
But it looks like this same test started failing on i686-pc-linux-gnu
(http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg01842.html), guessing for the
same reason. Not sure if there's some similar type option that can be added for
that target or whether '-w' should just be added to the testcase.