public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>,
	       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: Wed, 27 Jan 2016 19:29:00 -0000	[thread overview]
Message-ID: <56A91A7A.3060700@redhat.com> (raw)
In-Reply-To: <20160127185159.GT3017@tucnak.redhat.com>

On 01/27/2016 11:51 AM, Jakub Jelinek wrote:
> Hi!
>
> On Wed, Jan 27, 2016 at 11:17:18AM +0100, Richard Biener wrote:
>> No, simply warn and set TREE_NO_WARNING so cgraph doesn't warn again.
>
> This seems to work too, bootstrapped/regtested on x86_64-linux and
> i686-linux, ok for trunk?
>
> 2016-01-25  Jakub Jelinek  <jakub@redhat.com>
>
> 	PR debug/66869
> 	* c-decl.c (c_write_global_declarations_1): Warn with
> 	warn_unused_function if static prototype without definition
> 	is not C_DECL_USED.
>
> 	* gcc.dg/pr66869.c: New test.
OK.
jeff

  reply	other threads:[~2016-01-27 19:29 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
2016-01-27 10:17     ` Richard Biener
2016-01-27 18:52       ` Jakub Jelinek
2016-01-27 19:29         ` Jeff Law [this message]
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=56A91A7A.3060700@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=jakub@redhat.com \
    --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).