Bug 84392 - test case gcc.dg/graphite/uns-interchange-9.c and 3 others fail on power9
Summary: test case gcc.dg/graphite/uns-interchange-9.c and 3 others fail on power9
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: target (show other bugs)
Version: 8.0
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-14 21:02 UTC by seurer
Modified: 2018-02-15 16:28 UTC (History)
3 users (show)

See Also:
Host: powerpc64le-unknown-linux-gnu
Target: powerpc64le-unknown-linux-gnu
Build: powerpc64le-unknown-linux-gnu
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description seurer 2018-02-14 21:02:45 UTC
These 4 tests fail on power9

FAIL: gcc.dg/graphite/uns-interchange-9.c scan-tree-dump graphite "tiled"
FAIL: gcc.dg/graphite/interchange-3.c scan-tree-dump graphite "tiled"
FAIL: gcc.dg/graphite/interchange-7.c scan-tree-dump graphite "tiled"
FAIL: gcc.dg/graphite/interchange-9.c scan-tree-dump graphite "tiled"

They appear to be erratic in failing; while trying to track down an originating revision I was seeing some older revisions work and then later fail.

When they fail they all fail the same way:

spawn -ignore SIGHUP /home/seurer/gcc/build/gcc-trunk/gcc/xgcc -B/home/seurer/gcc/build/gcc-trunk/gcc/ /home/seurer/gcc/gcc-trunk/gcc/testsuite/gcc.dg/graphite/interchange-3.c -fno-diagnostics-show-caret -fdiagnostics-color=never -O2 -ffast-math -floop-nest-optimize -fdump-tree-graphite-all -lm -o ./interchange-3.exe
PASS: gcc.dg/graphite/interchange-3.c (test for excess errors)
. . .
PASS: gcc.dg/graphite/interchange-3.c execution test
FAIL: gcc.dg/graphite/interchange-3.c scan-tree-dump graphite "tiled"
Comment 1 Richard Biener 2018-02-15 13:21:30 UTC
which ISL version are you using?  Anything older than 0.18 is known to cause some of those fails.
Comment 2 seurer 2018-02-15 16:28:58 UTC
That could be it.  I started the tester over with a complete refresh of the source and haven't seen the failures since.