public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61018] [4.8/4.9/5 Regression] -Wvarargs does not print warning for member functions
Date: Tue, 24 Feb 2015 11:31:00 -0000	[thread overview]
Message-ID: <bug-61018-4-PyrJDhBv8X@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61018-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61018

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |jakub at gcc dot gnu.org
         Resolution|---                         |INVALID

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I really don't see why this is considered a bug.  Some diagnostics are simply
performed only on code that is actually used.  You can always use
-fkeep-inline-functions which causes it to warn, or just use the method.  If
you never use it, it isn't that important if it is broken.


      parent reply	other threads:[~2015-02-24 11:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 16:33 [Bug c++/61018] New: -Wvarargs does not print warning for memer functions bilbotheelffriend at gmail dot com
2014-11-10 13:41 ` [Bug c++/61018] -Wvarargs does not print warning for member functions redi at gcc dot gnu.org
2014-11-10 16:51 ` [Bug c++/61018] [5 Regression] " manu at gcc dot gnu.org
2014-12-01 12:01 ` [Bug c++/61018] [4.8/4.9/5 " rguenth at gcc dot gnu.org
2014-12-09 17:38 ` [Bug middle-end/61018] " jason at gcc dot gnu.org
2014-12-19 13:43 ` jakub at gcc dot gnu.org
2015-02-24 11:31 ` jakub at gcc dot gnu.org [this message]

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-61018-4-PyrJDhBv8X@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).