Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#9186 closed enhancement (fixed)

gcc-7.1.0

Reported by: bdubbs@… Owned by: Pierre Labastie
Priority: normal Milestone: 8.1
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

New major version. Wait for LFS update.

Change History (12)

comment:1 by Pierre Labastie, 4 years ago

Owner: changed from blfs-book@… to Pierre Labastie
Status: newassigned

comment:2 by Pierre Labastie, 4 years ago

LFS updated...

comment:3 by Pierre Labastie, 4 years ago

See Changes at https://gcc.gnu.org/gcc-7/changes.html A very important part:

Java (GCJ)

The GCC Java frontend and associated libjava runtime library have been removed from GCC.

So I guess the gcc-java page should be archived...

comment:4 by Pierre Labastie, 4 years ago

No failure in any test! Yet valgrind and gdb are installed.

comment:5 by bdubbs@…, 4 years ago

So it would appear that the five failed tests in LFS are due to missing test programs or the limited environment in Chapter 6 when gcc is built.

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/temp_directory_path.cc execution test

All in the libstdc++ section.

I have not investigated the reason for these failures, but they appear to be related.

in reply to:  5 comment:6 by Pierre Labastie, 4 years ago

Replying to bdubbs@…:

So it would appear that the five failed tests in LFS are due to missing test programs or the limited environment in Chapter 6 when gcc is built.

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/temp_directory_path.cc execution test

All in the libstdc++ section.

I have not investigated the reason for these failures, but they appear to be related.

I cannot tell for sure those tests are run, since they do not appear in the log if they do not fail. We can compare the number of tests. I have:

                === libstdc++ Summary ===

# of expected passes            11668
# of expected failures          66
# of unsupported tests          296

comment:7 by Pierre Labastie, 4 years ago

There are two new languages: "brig" (http://www.hsafoundation.com/hsa-foundation-announces-results-of-innovative-open-source-project/ and "jit" (https://gcc.gnu.org/wiki/JIT). I do not understand exactly what they do (specially jit), so I am not sure I want to include them. I'll mention them in the "Command Explanations".

comment:8 by Pierre Labastie, 4 years ago

Resolution: fixed
Status: assignedclosed

Fixed at r18694

comment:9 by bdubbs@…, 4 years ago

It looks like LFS runs the same number of tests:

      === libstdc++ Summary ===

# of expected passes    11663
# of unexpected failures   5
# of expected failures     66
# of unsupported tests     296

The only difference is the unexpected failures in LFS.

comment:10 by Pierre Labastie, 4 years ago

Actually, those tests only fail when run as root (as stated in the book). The reason is that they tests accessibility to files, and root has to much privs.

comment:11 by bdubbs@…, 4 years ago

Milestone: 8.1m8.1

Milestone renamed

comment:12 by bdubbs@…, 4 years ago

Milestone: m8.18.1

Milestone renamed

Note: See TracTickets for help on using tickets.