public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "leimaohui at cn dot fujitsu.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63908] New: [e500v2] "float_bessel"case failed on e500v2 platforms
Date: Mon, 17 Nov 2014 10:17:00 -0000 [thread overview]
Message-ID: <bug-63908-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63908
Bug ID: 63908
Summary: [e500v2] "float_bessel"case failed on e500v2 platforms
Product: gcc
Version: 4.9.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: leimaohui at cn dot fujitsu.com
I used yocto 1.7 to make a rootfs and toolchain.And then test LTP.
gcc :4.9.1
kernel :3.4.74
LTP version: 20120903
Some cases failed in powerpc e500v2. But these cases are PASS in i586 and
armv7.
'float_bessel' is one of the failed cases. The log likes below:
###################################
float_bessel 1 TPASS : Test passed
float_bessel 0 TINFO : float_bessel: will run for 500 loops; using . as a
data directory
float_bessel 0 TINFO : float_bessel: will run 5 functions, 20 threads per
function
float_bessel 0 TINFO : signal handler 1216373856 started
float_bessel 0 TINFO : Signal handler starts waiting...
float_bessel 0 TINFO : initial thread: Waiting for 100 threads to finish
sh: line 1: 12822 Aborted float_bessel -v
###################################
In addition,'float_exp_log','float_iperb','float_power'and 'float_trigo' are
failed and have the similar phenomenon.
Steps:
######
1. root@localhost:~# cd /opt/ltp/
2. root@localhost:/opt/ltp# ./runltp -s float_bessel
######
Is there anybody give me some suggestions?
next reply other threads:[~2014-11-17 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 10:17 leimaohui at cn dot fujitsu.com [this message]
2014-11-17 10:20 ` [Bug target/63908] " leimaohui at cn dot fujitsu.com
2014-11-17 16:18 ` joseph at codesourcery dot com
2014-11-28 17:31 ` joseph at codesourcery dot com
2014-12-11 7:38 ` leimaohui at cn dot fujitsu.com
2014-12-17 7:24 ` leimaohui at cn dot fujitsu.com
2014-12-17 7:34 ` leimaohui at cn dot fujitsu.com
2014-12-17 15:55 ` joseph at codesourcery dot com
2015-01-13 11:39 ` leimaohui at cn dot fujitsu.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-63908-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).