Opened 3 years ago
Closed 3 years ago
#4847 closed task (fixed)
gcc-11.1.0
Reported by: | Xi Ruoyao | Owned by: | Douglas R. Reno |
---|---|---|---|
Priority: | normal | Milestone: | 11.0 |
Component: | Book | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
The release branch of gcc-11 has been forked and it should be released in two or three weeks.
Change History (13)
comment:1 by , 3 years ago
comment:2 by , 3 years ago
Summary: | gcc-11.1.0 (wait for this version) → gcc-11.1.0 |
---|
The GCC developers are proud to announce another major GCC release, 11.1. This release switches the default debugging format to DWARF 5 [1] on most targets and switches the default C++ language version to -std=gnu++17. It makes great progress in the C++20 language support, both on the compiler and library sides [2], adds experimental C++23 support, some C2X enhancements, various optimization enhancements and bug fixes, several new hardware enablement changes and enhancements to the compiler back-ends and many other changes. Some code that compiled successfully with older GCC versions might require source changes, see http://gcc.gnu.org/gcc-11/porting_to.html for details.
comment:3 by , 3 years ago
comment:4 by , 3 years ago
It can be simplified to a sed: sed 's/amx_/amx-/' -i sysdeps/x86/tst-cpu-features-supports.c
.
comment:5 by , 3 years ago
constexpr-52830 and bad-mapper-3 FAIL.
asan_test.C, co-ret-17-void-ret-coro.C, pr95519-05-gro.C, pr80166.c no longer FAIL.
comment:7 by , 3 years ago
There is no result posted in gcc-testresults for 11.1.0 now.
I'll report these two to gcc bugzilla.
comment:8 by , 3 years ago
52830 is mentioned at https://gcc.gnu.org/pipermail/gcc-testresults/2021-April/685744.html. It's a tricky bug in GCC since 4.8. The status quo is actually better: at least the compiler won't crash, but it still rejects the valid code.
comment:9 by , 3 years ago
bad-mapper-3 does not FAIL on the completed LFS system. In the log it says:
Temporary failure in name resolution mapper 'localhost:172477262'
I'm not sure what happened in LFS chroot: in theory our minimal /etc/hosts
created in Chapter 7 should prevent this kind of issue.
comment:10 by , 3 years ago
I commented out the line for ::1 in /etc/hosts and this test FAILs again. So I think adding a line
::1 localhost
into chapter 7 /etc/hosts will prevent bad-mapper-3 failure.
comment:12 by , 3 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:13 by , 3 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Fixed at @d7a942197e713339d4dc1eedab4dafd4179a5cd8
It's scheduled to be released on Apr 27.
The new features are documented in https://gcc.gnu.org/gcc-11/changes.html. The breaking changes are documented in https://gcc.gnu.org/gcc-11/porting_to.html.