[Bug binutils/19900] New: runtest fails after make

[cryo_rebirth at yahoo dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19900

            Bug ID: 19900
           Summary: runtest fails after make
           Product: binutils
           Version: 2.26
            Status: NEW
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: cryo_rebirth at yahoo dot com
  Target Milestone: ---

Created attachment 9149
  --> https://sourceware.org/bugzilla/attachment.cgi?id=9149&action=edit
Complete output of make check in txt file.

I wanted to bring this to the attention of the developers.  Using standard
options, runtest seems to fail 16 tests unexpectedly.  I'm not sure what the
cause is, but is it expected behaviour or is there something wrong here?

configured with --enable-gold --enable-plugins --enable-vtable-verify
--with-shared

Used 

make GRAPHITE='-fprofile-generate -fprofile-dir=./profile -floop-interchange
-floop-strip-mine -floop-block -floop-unroll-and-jam -fgraphite-identity
-floop-nest-optimize' CFLAGS='-fuse-linker-plugin -mtls-dialect=gnu2
-ftree-parallelize-loops=4 ${GRAPHITE}' FFLAGS='${CFLAGS}'
LDFLAGS='-fuse-ld=gold ${CFLAGS}' CXXFLAGS='${CFLAGS}' USE='graphite'

make check

make GRAPHITE='-fprofile-use=./profile -floop-interchange -floop-strip-mine
-floop-block -floop-unroll-and-jam -fgraphite-identity -floop-nest-optimize'
CFLAGS='-fuse-linker-plugin -mtls-dialect=gnu2 -ftree-parallelize-loops=4
${GRAPHITE}' FFLAGS='${CFLAGS}' LDFLAGS='-fuse-ld=gold ${CFLAGS}'
CXXFLAGS='${CFLAGS}' USE='graphite'

Exact same errors occur with normal make as well, but might as well optimize
what I can.  -O3 won't even finish compiling, but it's semi-expected behaviour
at that level.  Included is the complete output of make check.

FAIL: Build copyreloc-main with PIE without -fPIE (1)
FAIL: Build copyreloc-main with PIE without -fPIE (1)
FAIL: Build copyreloc-main with PIE without -fPIE (2)
FAIL: Build copyreloc-main with PIE without -fPIE (2)
FAIL: Build pr17689 with PIE without -fPIE
FAIL: Build pr17689 with PIE without -fPIE
FAIL: Build pr17689 with PIE -z now without -fPIE
FAIL: Build pr17689 with PIE -z now without -fPIE
FAIL: Build pr17827 with PIE without -fPIE
FAIL: Build pr17827 with PIE without -fPIE
FAIL: Build pr18900a
FAIL: Build pr18900a
FAIL: Build pr18900b
FAIL: Build pr18900b
FAIL: Build gotpcrel1
FAIL: Build gotpcrel1
Running /home/d337z/Desktop/binutils-2.26/ld/testsuite/ld-xc16x/xc16x.exp ...
Running
/home/d337z/Desktop/binutils-2.26/ld/testsuite/ld-xstormy16/xstormy16.exp ...
Running /home/d337z/Desktop/binutils-2.26/ld/testsuite/ld-xtensa/coalesce.exp
...
Running
/home/d337z/Desktop/binutils-2.26/ld/testsuite/ld-xtensa/diff_overflow.exp ...
Running /home/d337z/Desktop/binutils-2.26/ld/testsuite/ld-xtensa/lcall.exp ...
Running /home/d337z/Desktop/binutils-2.26/ld/testsuite/ld-xtensa/xtensa.exp ...

                === ld Summary ===

# of expected passes            1365
# of unexpected failures        16
# of expected failures          57
# of untested testcases         1
# of unsupported tests          12
/home/d337z/Desktop/binutils-2.26/ld/ld-new 2.26.20160125

Makefile:3546: recipe for target 'check-DEJAGNU' failed
make[5]: *** [check-DEJAGNU] Error 1
make[5]: Leaving directory '/home/d337z/Desktop/binutils-2.26/ld'
Makefile:1866: recipe for target 'check-am' failed
make[4]: *** [check-am] Error 2
make[4]: Leaving directory '/home/d337z/Desktop/binutils-2.26/ld'
Makefile:1713: recipe for target 'check-recursive' failed
make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory '/home/d337z/Desktop/binutils-2.26/ld'
Makefile:1868: recipe for target 'check' failed
make[2]: *** [check] Error 2
make[2]: Leaving directory '/home/d337z/Desktop/binutils-2.26/ld'
Makefile:7531: recipe for target 'check-ld' failed
make[1]: *** [check-ld] Error 2
make[1]: Leaving directory '/home/d337z/Desktop/binutils-2.26'
Makefile:2199: recipe for target 'do-check' failed
make: *** [do-check] Error 2

-- 
You are receiving this mail because:
You are on the CC list for the bug.