public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
	       Marek Polacek <polacek@redhat.com>,
	Jason Merrill <jason@redhat.com>,
	       Jan Hubicka <hubicka@ucw.cz>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [C PATCH] Fix -Wunused-function (PR debug/66869)
Date: Tue, 26 Jan 2016 16:18:00 -0000	[thread overview]
Message-ID: <20160126161813.GB3017@tucnak.redhat.com> (raw)
In-Reply-To: <CAFiYyc12VJd=HcmH6YsnwVWinfzBnMzq-WyujU85eg05LCUReg@mail.gmail.com>

On Tue, Jan 26, 2016 at 04:21:08PM +0100, Richard Biener wrote:
> > --- gcc/c/c-decl.c.jj   2016-01-21 00:41:47.000000000 +0100
> > +++ gcc/c/c-decl.c      2016-01-25 16:36:31.973504082 +0100
> > @@ -10741,11 +10741,19 @@ c_write_global_declarations_1 (tree glob
> >        if (TREE_CODE (decl) == FUNCTION_DECL
> >           && DECL_INITIAL (decl) == 0
> >           && DECL_EXTERNAL (decl)
> > -         && !TREE_PUBLIC (decl)
> > -         && C_DECL_USED (decl))
> > +         && !TREE_PUBLIC (decl))
> >         {
> > -         pedwarn (input_location, 0, "%q+F used but never defined", decl);
> > -         TREE_NO_WARNING (decl) = 1;
> > +         if (C_DECL_USED (decl))
> > +           {
> > +             pedwarn (input_location, 0, "%q+F used but never defined", decl);
> > +             TREE_NO_WARNING (decl) = 1;
> > +           }
> > +         /* For -Wunused-function push the unused statics into cgraph,
> > +            so that check_global_declaration emits the warning.  */
> > +         else if (warn_unused_function
> > +                  && ! DECL_ARTIFICIAL (decl)
> > +                  && ! TREE_NO_WARNING (decl))
> > +           cgraph_node::get_create (decl);
> 
> Err, so why not warn here directly?

You mean check if it has a cgraph node (i.e. get instead of get_create) and
if it doesn't, warn?  What I'm worried in that case is that it might have a
cgraph node created later on for whatever reason and that we'll get double
warning (from here and from cgraphunit.c (check_global_declaration)).
I can try it though.

	Jakub

  reply	other threads:[~2016-01-26 16:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 20:38 Jakub Jelinek
2016-01-26 15:21 ` Richard Biener
2016-01-26 16:18   ` Jakub Jelinek [this message]
2016-01-27 10:17     ` Richard Biener
2016-01-27 18:52       ` Jakub Jelinek
2016-01-27 19:29         ` Jeff Law
2016-01-28 20:15           ` [C++ " Jakub Jelinek
2016-01-29 10:25             ` Jason Merrill
2016-01-29 10:35               ` Jakub Jelinek
2016-01-29 10:47                 ` Jason Merrill
2016-01-29 12:31                 ` Jakub Jelinek
2016-02-03 16:05                   ` Jason Merrill

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=20160126161813.GB3017@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=jason@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=polacek@redhat.com \
    --cc=richard.guenther@gmail.com \
    /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).