This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/54868] [4.8 Regression]gcc.dg/tree-ssa/forwprop-22.c FAILs
- From: "glisse at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 11 Oct 2012 09:57:19 +0000
- Subject: [Bug tree-optimization/54868] [4.8 Regression]gcc.dg/tree-ssa/forwprop-22.c FAILs
- Auto-submitted: auto-generated
- References: <bug-54868-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54868
--- Comment #6 from Marc Glisse <glisse at gcc dot gnu.org> 2012-10-11 09:57:19 UTC ---
(In reply to comment #4)
> Have a look at vect.exp: there are specific naming conventions for
> testcases that control how they are compiled.
Gah, you are right, thanks. I wish the testsuite weren't that complicated, with
funny different rules in every sub-directory...
I am tempted to create a new subdirectory (with its own .exp file) for generic
vector tests that are not vectorizer tests. A directory where things like
dg-require-effective-target vect_double would actually do what they say... But
check_vect_support_and_set_flags is still not ideal, on x86 it uses -msse2 and
I'd rather have either -mavx2 (compile-only) or whatever the machine supports
(likely at least -msse4 these days).
I'll see if just renaming the testcase in the vect directory is enough for this
testcase.