From: Rusty Lynch <rusty@linux.co.intel.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Request to remove -Wfno-format
Date: Thu Feb 12 12:52:32 2004 [thread overview]
Message-ID: <20040212185222.GA30675@penguin.co.intel.com> (raw)
In-Reply-To: <200402121839.i1CIdRaY027264@penguin.co.intel.com>
On Thu, Feb 12, 2004 at 10:39:27AM -0800, Rusty Lynch wrote:
> While porting to 2.6 I am just using the 2.6 build system and putting off
> the autoconfig stuff till later. As a result of this I am seeing a ton of
> additional warning messages due to the fact that the ocfs2 build system is
> including "-Wno-format".
>
> Is there a good reason for adding the "-Wno-format" option to the build?
>
> The kind of mistakes that are being ignored are ==>
>
> LOG_TRACE_ARGS("found some data to free (%u.%u)\n",
> HI(cur_extent->this_ext), LO(cur_extent->this_ext));
> alloc.c: In function `ocfs_kill_this_tree':
> alloc.c:1620: warning: unsigned int format, long unsigned int arg (arg 2)
> alloc.c:1620: warning: unsigned int format, long unsigned int arg (arg 3)
> alloc.c:1638: warning: unsigned int format, long unsigned int arg (arg 2)
> alloc.c:1638: warning: unsigned int format, long unsigned int arg (arg 3)
>
>
> and ==>
> LOG_TRACE_ARGS("Popping this header (%u.%u)\n",
> HI(AllocExtent->this_ext),
> LO(AllocExtent->this_ext),
> AllocExtent->next_free_ext);
> alloc.c:2079: warning: unsigned int format, long unsigned int arg (arg 2)
> alloc.c:2079: warning: unsigned int format, long unsigned int arg (arg 3)
> alloc.c:2079: warning: too many arguments for format
> alloc.c:2099: warning: unsigned int format, long unsigned int arg (arg 2)
> alloc.c:2099: warning: unsigned int format, long unsigned int arg (arg 3)
>
>
> If it is ok, I would like to make the build more strict, and treat each of
> the warnings as bugs.
>
> --rusty
and here is a quick patch to remove the flag
Index: src/Makefile
===================================================================
--- src/Makefile (revision 31)
+++ src/Makefile (working copy)
@@ -2,7 +2,7 @@
include $(TOPDIR)/Preamble.make
-WARNINGS = -Wall -Wstrict-prototypes -Wno-format
+WARNINGS = -Wall -Wstrict-prototypes
ifneq ($(OCFS_PROCESSOR),x86_64)
WARNINGS += -Wmissing-prototypes -Wmissing-declarations
next prev parent reply other threads:[~2004-02-12 12:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 12:39 [Ocfs2-devel] Request to remove -Wfno-format Rusty Lynch
2004-02-12 12:52 ` Rusty Lynch [this message]
2004-02-12 14:30 ` Manish Singh
2004-02-13 16:10 ` Rusty Lynch
2004-02-12 21:44 ` Manish Singh
2004-02-13 16:10 ` Rusty Lynch
2004-02-13 16:15 ` Manish Singh
2004-02-13 16:24 ` Rusty Lynch
2004-02-13 18:07 ` Rusty Lynch
2004-02-13 19:04 ` Manish Singh
2004-02-13 19:37 ` Rusty Lynch
2004-02-13 21:05 ` Manish Singh
2004-02-13 21:09 ` Rusty Lynch
2004-02-13 21:18 ` Mark Fasheh
2004-02-16 15:01 ` Rusty Lynch
-- strict thread matches above, loose matches on Subject: below --
2004-02-17 8:50 Cahill, Ben M
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=20040212185222.GA30675@penguin.co.intel.com \
--to=rusty@linux.co.intel.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.