public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/57563] New: Lots of Cilk+ failures on i686-linux
Date: Fri, 07 Jun 2013 19:37:00 -0000	[thread overview]
Message-ID: <bug-57563-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 57563
           Summary: Lots of Cilk+ failures on i686-linux
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jakub at gcc dot gnu.org
                CC: bviyer at gcc dot gnu.org
            Target: i686-linux

If you do
make check-gcc RUNTESTFLAGS='--target_board=unix/-m32 cilk-plus.exp'
on x86_64-linux (or just make check-gcc RUNTESTFLAGS=cilk-plus.exp on
i686-linux), I'm seeing tons of FAILs that don't show up in x86_64 64-bit
testing:
FAIL: c-c++-common/cilk-plus/AN/builtin_fn_mutating.c  -O3 -fcilkplus execution
test
FAIL: c-c++-common/cilk-plus/AN/builtin_fn_mutating.c  -g -O3 -fcilkplus
execution test
FAIL: c-c++-common/cilk-plus/AN/builtin_fn_mutating.c  -O3 -ftree-vectorize
-fcilkplus -g execution test
FAIL: c-c++-common/cilk-plus/AN/builtin_fn_custom.c  -fcilkplus -std=c99
execution test
FAIL: c-c++-common/cilk-plus/AN/builtin_fn_mutating.c  -fcilkplus -std=c99
execution test
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -std=c99
(internal compiler error)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -std=c99
(test for excess errors)
FAIL: c-c++-common/cilk-plus/AN/builtin_fn_custom.c  -fcilkplus -O0 -std=c99
execution test
FAIL: c-c++-common/cilk-plus/AN/builtin_fn_mutating.c  -fcilkplus -O0 -std=c99
execution test
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -O0 -std=c99
(internal compiler error)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -O0 -std=c99
(test for excess errors)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -O1 -std=c99
(internal compiler error)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -O1 -std=c99
(test for excess errors)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -O2
-ftree-vectorize -std=c99 (internal compiler error)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -O2
-ftree-vectorize -std=c99 (test for excess errors)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -O3 -std=c99
(internal compiler error)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -O3 -std=c99
(test for excess errors)
FAIL: c-c++-common/cilk-plus/AN/builtin_fn_custom.c  -fcilkplus -g -std=c99
execution test
FAIL: c-c++-common/cilk-plus/AN/builtin_fn_mutating.c  -fcilkplus -g -std=c99
execution test
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -g -std=c99
(internal compiler error)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -g -std=c99
(test for excess errors)
FAIL: c-c++-common/cilk-plus/AN/builtin_fn_custom.c  -fcilkplus -g -O0 -std=c99
execution test
FAIL: c-c++-common/cilk-plus/AN/builtin_fn_mutating.c  -fcilkplus -g -O0
-std=c99 execution test
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -g -O0
-std=c99 (internal compiler error)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -g -O0
-std=c99 (test for excess errors)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -g -O1
-std=c99 (internal compiler error)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -g -O1
-std=c99 (test for excess errors)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -g -O2
-ftree-vectorize -std=c99 (internal compiler error)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -g -O2
-ftree-vectorize -std=c99 (test for excess errors)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -g -O3
-std=c99 (internal compiler error)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -fcilkplus -g -O3
-std=c99 (test for excess errors)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -O3 -ftree-vectorize
-std=c99 -g -fcilkplus (internal compiler error)
FAIL: c-c++-common/cilk-plus/AN/builtin_func_double.c  -O3 -ftree-vectorize
-std=c99 -g -fcilkplus (test for excess errors)


             reply	other threads:[~2013-06-07 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 19:37 jakub at gcc dot gnu.org [this message]
2013-06-08 19:07 ` [Bug c/57563] " mpolacek at gcc dot gnu.org
2013-10-21 20:48 ` mpolacek at gcc dot gnu.org

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-57563-4@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: link
Be 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).