This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/22664] New warning of GCC8
- From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 03 Jan 2018 13:49:41 +0000
- Subject: [Bug libc/22664] New warning of GCC8
- Auto-submitted: auto-generated
- References: <bug-22664-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22664
Joseph Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |2.27
--- Comment #1 from Joseph Myers <jsm28 at gcc dot gnu.org> ---
https://sourceware.org/ml/libc-testresults/2018-q1/msg00017.html
shows clean builds with GCC r256073 for glibc mainline. Thus all these
warnings must be fixed or disabled or set not to cause errors, or the build
would fail. Cherry-picking fixes to release branches is welcome as usual (post
cherry-picked fixes to libc-stable).
https://sourceware.org/glibc/wiki/GlibcGit#CherryPickCommit
(If building with an option other than -O2, other warnings might appear; any
such warnings on mainline should be considered a separate issue. We don't yet
have clean builds and tests with -Os, quite likely not with other -O options
either.)
In general, reports of build warnings for non-mainline versions are not
particularly useful, as all such fixes will go quickly on mainline, but may or
may not be backported depending on whether anyone is actually trying to build
older glibc with newer GCC.
--
You are receiving this mail because:
You are on the CC list for the bug.