public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/46312] gcc.dg/vec-scal-opt2.c fails for ARM targets. Date: Fri, 05 Nov 2010 11:44:00 -0000 [thread overview] Message-ID: <bug-46312-4-r4AT7UTBkF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46312-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46312 --- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> 2010-11-05 11:43:48 UTC --- On Fri, 5 Nov 2010, jakub at gcc dot gnu.org wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46312 > > Jakub Jelinek <jakub at gcc dot gnu.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |jakub at gcc dot gnu.org > > --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-11-05 11:39:19 UTC --- > It fails even on i686-linux: Hm, it tested ok on x86_64 with -m32. > Executing on host: /usr/src/gcc/obj333/gcc/xgcc -B/usr/src/gcc/obj333/gcc/ > /usr/src/gcc/gcc/testsuite/gcc.dg/vec-scal-opt.c -O -fdump-tree-veclower -S > -o vec-scal-opt.s (timeout = 300) > PASS: gcc.dg/vec-scal-opt.c (test for excess errors) > FAIL: gcc.dg/vec-scal-opt.c scan-tree-dump-times veclower ">> k.[0-9_]*" 1 > Executing on host: /usr/src/gcc/obj333/gcc/xgcc -B/usr/src/gcc/obj333/gcc/ > /usr/src/gcc/gcc/testsuite/gcc.dg/vec-scal-opt1.c -O -fdump-tree-veclower -S > -o vec-scal-opt1.s (timeout = 300) > PASS: gcc.dg/vec-scal-opt1.c (test for excess errors) > FAIL: gcc.dg/vec-scal-opt1.c scan-tree-dump-times veclower ">> 2" 1 > Executing on host: /usr/src/gcc/obj333/gcc/xgcc -B/usr/src/gcc/obj333/gcc/ > /usr/src/gcc/gcc/testsuite/gcc.dg/vec-scal-opt2.c -O -fdump-tree-veclower -S > -o vec-scal-opt2.s (timeout = 300) > PASS: gcc.dg/vec-scal-opt2.c (test for excess errors) > FAIL: gcc.dg/vec-scal-opt2.c scan-tree-dump-times veclower ">> 2" 1 > Executing on host: /usr/src/gcc/obj333/gcc/xgcc -B/usr/src/gcc/obj333/gcc/ > /usr/src/gcc/gcc/testsuite/gcc.dg/vector-1.c -S -o vector-1.s (timeout = > 300) > /usr/src/gcc/gcc/testsuite/gcc.dg/vector-1.c: In function 'f': > /usr/src/gcc/gcc/testsuite/gcc.dg/vector-1.c:13:7: error: wrong type argument > to bit-complement > compiler exited with status 1 > output is: > /usr/src/gcc/gcc/testsuite/gcc.dg/vector-1.c: In function 'f': > /usr/src/gcc/gcc/testsuite/gcc.dg/vector-1.c:13:7: error: wrong type argument > to bit-complement > > I guess the bug is that the testcase should be put into gcc.dg/vect/ rather > than gcc.dg/ directly. But that enables -ftree-vectorize, but ok - I guess that doesn't matter too much.
next prev parent reply other threads:[~2010-11-05 11:44 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-05 11:22 [Bug tree-optimization/46312] New: " ramana at gcc dot gnu.org 2010-11-05 11:29 ` [Bug tree-optimization/46312] " rguenth at gcc dot gnu.org 2010-11-05 11:39 ` jakub at gcc dot gnu.org 2010-11-05 11:42 ` ramana.r at gmail dot com 2010-11-05 11:44 ` rguenther at suse dot de [this message] 2010-11-09 10:41 ` rguenth at gcc dot gnu.org 2010-11-09 13:46 ` rguenth at gcc dot gnu.org 2010-11-09 13:46 ` rguenth at gcc dot gnu.org 2010-11-12 10:57 ` ramana at gcc dot gnu.org 2010-11-12 10:58 ` ramana at gcc dot gnu.org 2010-11-12 11:54 ` jakub at gcc dot gnu.org 2010-11-17 10:20 ` irar at gcc dot gnu.org 2010-11-21 8:03 ` irar at il dot ibm.com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-46312-4-r4AT7UTBkF@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).