sean-m
/
kendryte-gnu-toolchain
mirror of https://github.com/kendryte/kendryte-gnu-toolchain.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Whitelist a log1p failure in newlib 

This might be an actaul newlib bug: it's not providing a range error
when taking log1p of -1e80, but it appears that this triggered a glibc
bug from a while ago that may have not been fixed in newlib.  I'm not
sure why the bug is just manifesting now (the newlib sources haven't
changed for a long time), but the glibc version has some macros that
force the evaluation of particular floating-point expressions (one of
which produces the range error) that don't exist in newlib.

I'm OK whitelisting the error for the next release, despite it
technically being a regression.  log1p isn't a standard function, and I
doubt embedded users are going to notice.  That said, we should still
fix it.
develop
Palmer Dabbelt 2017-12-16 10:19:15 -08:00
parent b7283fc426
commit acc92a31c9
2 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
test/gcc-newlib/rv32imafc-ilp32f.log
View File

@ -7,3 +7,11 @@ build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/ipa/iinline-cstag
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/tree-ssa/pr42585.c scan-tree-dump-times optimized "struct _fat_ptr _T2" 0
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/tree-ssa/pr42585.c scan-tree-dump-times optimized "struct _fat_ptr _ans" 0
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/tree-ssa/pr81588.c scan-tree-dump-times reassoc1 "Optimizing range test [^\n\r]* and comparison" 1
# log1p doesn't return a range error on newlib
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -O0 execution test
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -O1 execution test
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -O2 execution test
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -O3 -g execution test
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -Os execution test

8
test/gcc-newlib/rv64imafdc-lp64d.log
View File

@ -7,3 +7,11 @@ build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/ipa/iinline-cstag
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/tree-ssa/pr42585.c scan-tree-dump-times optimized "struct _fat_ptr _T2" 0
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/tree-ssa/pr42585.c scan-tree-dump-times optimized "struct _fat_ptr _ans" 0
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/tree-ssa/pr81588.c scan-tree-dump-times reassoc1 "Optimizing range test [^\n\r]* and comparison" 1
# log1p doesn't return a range error on newlib
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -O0 execution test
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -O1 execution test
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -O2 execution test
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -O3 -g execution test
build-gcc-newlib-stage2/gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/torture/pr68264.c -Os execution test