public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/105404] new version of zlib
Date: Wed, 04 May 2022 09:39:32 +0000	[thread overview]
Message-ID: <bug-105404-4-9F5FJyYl7y@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

--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to David Binderman from comment #7)
> (In reply to Martin Liška from comment #6)
> > Can't see the warning when I build the current zlib library with clang.
> 
> You might need to switch on -Wall or (more likely) -Wextra.

Well, I use default options for that.

> 
> > Can you please paste a build log?
> 
> Not easily. Here is one example warning, amongst many:
> 
> ../../trunk.git/zlib/uncompr.c:86:13: warning: a function declaration
> without a prototype is deprecated in all versions of C and is not supported
> in C2x [-Wdeprecated-non-prototype]
> 
> As I say, pattern /zlib/.*-Wdeprecated-non-prototype would probably work.

Sure, please send a patch for it.

  parent reply	other threads:[~2022-05-04  9:39 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
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 [this message]
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-9F5FJyYl7y@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).