public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/105404] new version of zlib
Date: Thu, 28 Apr 2022 08:28:22 +0000 [thread overview]
Message-ID: <bug-105404-4-VeS8CxhO0Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105404-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105404
David Binderman <dcb314 at hotmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mliska at suse dot cz
--- Comment #4 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Jonathan Wakely from comment #3)
> No, because we don't use the buggy Z_FIXED feature.
Righto. Presumably the upgrade can be postponed until after the current
version of gcc trunk is released.
I note with interest that there is a lot of old K'n'R style code in the zlib
library
which clang warns won't compile with c2x.
It might be worth adding an extra filter to file
contrib/filter-clang-warnings.py to remove such warnings.
Pattern /zlib/.*-Wdeprecated-non-prototype would probably work.
next prev parent reply other threads:[~2022-04-28 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 9:10 [Bug c/105404] New: " dcb314 at hotmail dot com
2022-04-27 9:28 ` [Bug c/105404] " redi at gcc dot gnu.org
2022-04-27 10:04 ` [Bug other/105404] " dcb314 at hotmail dot com
2022-04-27 10:21 ` redi at gcc dot gnu.org
2022-04-28 8:28 ` dcb314 at hotmail dot com [this message]
2022-04-28 8:29 ` marxin at gcc dot gnu.org
2022-05-03 12:10 ` marxin at gcc dot gnu.org
2022-05-03 17:54 ` dcb314 at hotmail dot com
2022-05-04 9:39 ` marxin at gcc dot gnu.org
2023-04-06 5:01 ` pinskia at gcc dot gnu.org
2023-04-06 5:08 ` pinskia at gcc dot gnu.org
2023-04-06 5:38 ` pinskia at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-105404-4-VeS8CxhO0Y@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).