qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [5929] Enable gcc flag -Wmissing-prototypes
Date: Sun, 07 Dec 2008 19:15:19 +0000	[thread overview]
Message-ID: <E1L9P67-00010C-GI@cvs.savannah.gnu.org> (raw)

Revision: 5929
          http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5929
Author:   blueswir1
Date:     2008-12-07 19:15:17 +0000 (Sun, 07 Dec 2008)

Log Message:
-----------
Enable gcc flag -Wmissing-prototypes

Modified Paths:
--------------
    trunk/Makefile.target
    trunk/configure

Modified: trunk/Makefile.target
===================================================================
--- trunk/Makefile.target	2008-12-07 19:13:12 UTC (rev 5928)
+++ trunk/Makefile.target	2008-12-07 19:15:17 UTC (rev 5929)
@@ -73,7 +73,7 @@
 
 # We require -O2 to avoid the stack setup prologue in EXIT_TB
 OP_CFLAGS := -O2 -g -fno-strict-aliasing
-OP_CFLAGS += -Wall -Wundef -Wendif-labels -Wwrite-strings
+OP_CFLAGS += -Wall -Wundef -Wendif-labels -Wwrite-strings -Wmissing-prototypes
 
 # cc-option
 # Usage: OP_CFLAGS+=$(call cc-option, -falign-functions=0, -malign-functions=0)

Modified: trunk/configure
===================================================================
--- trunk/configure	2008-12-07 19:13:12 UTC (rev 5928)
+++ trunk/configure	2008-12-07 19:15:17 UTC (rev 5929)
@@ -381,7 +381,7 @@
 
 # default flags for all hosts
 CFLAGS="$CFLAGS -O2 -g -fno-strict-aliasing"
-CFLAGS="$CFLAGS -Wall -Wundef -Wendif-labels -Wwrite-strings"
+CFLAGS="$CFLAGS -Wall -Wundef -Wendif-labels -Wwrite-strings -Wmissing-prototypes"
 LDFLAGS="$LDFLAGS -g"
 if test "$werror" = "yes" ; then
 CFLAGS="$CFLAGS -Werror"

                 reply	other threads:[~2008-12-07 19:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E1L9P67-00010C-GI@cvs.savannah.gnu.org \
    --to=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).