[Bug target/63908] New: [e500v2] "float_bessel"case failed on e500v2 platforms

[Bug target/63908] New: [e500v2] "float_bessel"case failed on e500v2 platforms

[leimaohui at cn dot fujitsu.com]

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?

[Bug target/63908] [e500v2] "float_bessel"case failed on e500v2 platforms

[leimaohui at cn dot fujitsu.com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63908

--- Comment #1 from leimaohui <leimaohui at cn dot fujitsu.com> ---
I changed the gcc from 4.9.1 to 4.9.2 in yocto,and tested these cases.
The results are the same.

But when I changed the gcc to 4.8.2,the results of these cases are PASS.

[Bug target/63908] [e500v2] "float_bessel"case failed on e500v2 platforms

[joseph at codesourcery dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63908

--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Mon, 17 Nov 2014, leimaohui at cn dot fujitsu.com wrote:

> kernel :3.4.74

Don't expect particularly meaningful floating-point results on e500 for 
any kernel without my six-patch series that went into 3.14.

[Bug target/63908] [e500v2] "float_bessel"case failed on e500v2 platforms

[joseph at codesourcery dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63908

--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
In such a case you need to debug the system as a whole until you have 
isolated the bug to one component and can then report it to that component 
with evidence for where the bug is.

It's quite possible pthread_exit could run into unwind info problems - 
make sure you have Olivier Hainque's patches 
<https://gcc.gnu.org/ml/gcc-patches/2014-11/msg02975.html> backported, 
together with my fix

2014-10-25  Joseph Myers  <joseph@codesourcery.com>

        * config/rs6000/rs6000.c (rs6000_hard_regno_nregs_internal): Do
        not allow e500 double in registers not satisyfing
        SPE_SIMD_REGNO_P.

before unwinding will work for e500v2 with 4.9.

[Bug target/63908] [e500v2] "float_bessel"case failed on e500v2 platforms

[leimaohui at cn dot fujitsu.com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63908

--- Comment #5 from leimaohui <leimaohui at cn dot fujitsu.com> ---
Thanks,these patches do work.

I used gcc(master:7a542b16e34cfb40fe37fab74a119e80a1a55587) to do a test likes
below:

kernel : 3.14.19
ltp:20120903

|     test     |with these patches|remove these patches|
|sem02's result|     PASS         |    FAIL            |

I want to backport these patches to 4.9.1,but Iwas failed。
There are too many differents between 4.9.1 and the master.

Can you give some help?

And I want to know when will these patches be backported to 4.9 branch.
>From gcc-bugs-return-470210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Dec 11 08:30:22 2014
Return-Path: <gcc-bugs-return-470210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25203 invoked by alias); 11 Dec 2014 08:30:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24603 invoked by uid 48); 11 Dec 2014 08:30:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/64260] [5 Regression] wrong code at -O1 on x86_64-linux-gnu
Date: Thu, 11 Dec 2014 08:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-64260-4-nMgZByhBfK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64260-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64260-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-12/txt/msg01217.txt.bz2
Content-length: 865

https://gcc.gnu.org/bugzilla/show_bug.cgi?idd260

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-12-11
                 CC|                            |jakub at gcc dot gnu.org
   Target Milestone|---                         |5.0
            Summary|wrong code at -O1 on        |[5 Regression] wrong code
                   |x86_64-linux-gnu            |at -O1 on x86_64-linux-gnu
     Ever confirmed|0                           |1

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yes, r217646 again.  I think we should gather testcases from all the dup PRs
and commit them after the fix is committed.

[Bug target/63908] [e500v2] "float_bessel"case failed on e500v2 platforms

[leimaohui at cn dot fujitsu.com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63908

--- Comment #6 from leimaohui <leimaohui at cn dot fujitsu.com> ---
Created attachment 34294
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34294&action=edit
the patch backport to gcc 4.9.1

[Bug target/63908] [e500v2] "float_bessel"case failed on e500v2 platforms

[leimaohui at cn dot fujitsu.com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63908

leimaohui <leimaohui at cn dot fujitsu.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |e500v2

--- Comment #7 from leimaohui <leimaohui at cn dot fujitsu.com> ---
(In reply to leimaohui from comment #6)
> Created attachment 34294 [details]
> the patch backport to gcc 4.9.1

I tried to backport these patches to gcc4.9.1(about the packport,please see the
attachments).
But build error appeared as following.
-------------------------------------
powerpc-poky-linux-gnuspe-gcc  -m32 -mcpu=8548 -mabi=spe -mspe
-mfloat-gprs=double
--sysroot=/poky-build-powerpc-p1020-gcc-4.9.1/tmp/sysroots/ubinux-p1020rdb -O2
-pipe -g -feliminate-unused-debug-types -fstack-protector-all
-D_FORTIFY_SOURCE=2 -O2  -O2 -pipe -g -feliminate-unused-debug-types
-fstack-protector-all -D_FORTIFY_SOURCE=2 -DIN_GCC  -DCROSS_DIRECTORY_STRUCTURE
 -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition  -isystem ./include   -fPIC -mlong-double-128
-mno-minimal-toc -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector
-Dinhibit_libc  -fPIC -mlong-double-128 -mno-minimal-toc -I. -I.
-I/poky-build-powerpc-p1020-gcc-4.9.1/tmp/work/ppce500v2-poky-linux-gnuspe/libgcc-initial/4.9.1-r0/gcc-4.9.1/build.powerpc-poky-linux-gnuspe.powerpc-poky-linux-gnuspe/powerpc-poky-linux-gnuspe/libgcc/../.././gcc
-I/poky-build-powerpc-p1020-gcc-4.9.1/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/libgcc
-I/poky-build-powerpc-p1020-gcc-4.9.1/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/libgcc/.
-I/poky-build-powerpc-p1020-gcc-4.9.1/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/libgcc/../gcc
-I/poky-build-powerpc-p1020-gcc-4.9.1/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/libgcc/../include
 -DHAVE_CC_TLS  -o _addvdi3.o -MT _addvdi3.o -MD -MP -MF _addvdi3.dep
-DL_addvdi3 -c
/poky-build-powerpc-p1020-gcc-4.9.1/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/libgcc/libgcc2.c
-fvisibility=hidden -DHIDE_EXPORTS
/poky-build-powerpc-p1020-gcc-4.9.1/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/libgcc/unwind-dw2.c:
In function 'uw_init_context_1':
/poky-build-powerpc-p1020-gcc-4.9.1/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/libgcc/unwind-dw2.c:1593:1:
internal compiler error: Segmentation fault
 }
 ^
-------------------------------------
I don't know if there is more work I have to do.

Can you give me some suggestions?

[Bug target/63908] [e500v2] "float_bessel"case failed on e500v2 platforms

[joseph at codesourcery dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63908

--- Comment #8 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Olivier Hainque referred to having a 4.9 version of his patch, I suggest 
you ask him.

[Bug target/63908] [e500v2] "float_bessel"case failed on e500v2 platforms

[leimaohui at cn dot fujitsu.com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63908

--- Comment #9 from leimaohui <leimaohui at cn dot fujitsu.com> ---
(In reply to joseph@codesourcery.com from comment #8)
> Olivier Hainque referred to having a 4.9 version of his patch, I suggest 
> you ask him.

Will these patches be backported to gcc 4.9.3 ?