On 08/10/2018 05:44 PM, Ken Moffat wrote:
On Fri, Aug 10, 2018 at 04:18:23PM -0500, Bruce Dubbs wrote:
On 08/10/2018 03:54 PM, Ken Moffat wrote:
On my most recent build (LFS-svn-2018-07-26 so still using
glibc-2.27) I noticed that my toolchain test results (on an AMD
Fam15h machine, which is slow) did not totally match what the book
said:
glibc-2.27 : only two failures,
FAIL: misc/tst-preadvwritev2
FAIL: misc/tst-preadvwritev64v2
On i7:
075-glibc-2.28:FAIL: inet/tst-idna_name_classify
075-glibc-2.28:FAIL: misc/tst-ttyname
Note that this is in chroot. We run these as root and I did not check as a
non-privileged user like we do in coreutils.
binutils-2.31.1
No failures, and specifically
PASS: debug_msg.sh
Is this done in chroot?
Yes, these are all from chroot, and I run the LFS tests (except bash,
coreutils, util-linux) as root.
gcc-8.2.0
for g++, two unexpected failures for g++.dg/pr83239.C for
-std=gnu++11 and -std=gnu++14
(no big deal)
Yes, I got those also.
for libstdc++ _14_ unexpected failures in 27_io/filesystem (eight)
and experimental/filesystem (six) - the book only mentions six
The six failures in 27_io/filesystem and experimental/filesystem are the
same.
I have two more in 27_io/filesystem :
FAIL: 27_io/filesystem/iterators/directory_iterator.cc execution test
FAIL: 27_io/filesystem/iterators/recursive_directory_iterator.cc execution test
FAIL: 27_io/filesystem/operations/exists.cc execution test
FAIL: 27_io/filesystem/operations/is_empty.cc execution test
FAIL: 27_io/filesystem/operations/remove.cc execution test
FAIL: 27_io/filesystem/operations/status.cc execution test
FAIL: 27_io/filesystem/operations/symlink_status.cc execution test
^^^ these two
FAIL: 27_io/filesystem/operations/temp_directory_path.cc execution test
FAIL: experimental/filesystem/iterators/directory_iterator.cc execution test
FAIL: experimental/filesystem/iterators/recursive_directory_iterator.cc
execution test
FAIL: experimental/filesystem/operations/exists.cc execution test
FAIL: experimental/filesystem/operations/is_empty.cc execution test
FAIL: experimental/filesystem/operations/remove.cc execution test
FAIL: experimental/filesystem/operations/temp_directory_path.cc execution test
And my total is
# of unexpected failures 14
but the book says to expect 6.
I intend to reword what we have. Doing 'grep Summary -A6 086-gcc-8.2.0'
I get some weird output. For example
=== libstdc++ Summary ===
# of expected passes 530
# of unsupported tests 6
=== libstdc++ Summary ===
# of expected passes 729
# of unexpected failures 3
# of unsupported tests 4
=== libstdc++ Summary ===
# of expected passes 745
# of unexpected failures 2
# of expected failures 1
# of unsupported tests 11
--
=== libstdc++ Summary ===
# of expected passes 804
# of unexpected failures 1
# of unsupported tests 3
=== libstdc++ Summary ===
# of expected passes 667
# of unexpected failures 3
# of unsupported tests 5
=== libstdc++ Summary ===
# of expected passes 635
# of unsupported tests 3
=== libstdc++ Summary ===
# of expected passes 749
# of unsupported tests 4
=== libstdc++ Summary ===
# of expected passes 475
# of unexpected failures 5
# of unsupported tests 4
That adds to 14 unexpected but I think that, for instance:
FAIL: 27_io/filesystem/operations/exists.cc execution test
FAIL: experimental/filesystem/operations/exists.cc execution test
are the same failure. I really count 8 unique failures in libstdc++
(and 2 in g++ [both pr83239.C])
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
