From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: kai@germaschewski.name, linux-kernel@vger.kernel.org,
Dave Jones <davej@redhat.com>,
linux-arch@vger.kernel.org
Subject: Re: [2.6 patch] add -Werror-implicit-function-declaration to CFLAGS
Date: Fri, 7 Jul 2006 05:36:30 +0200 [thread overview]
Message-ID: <20060707033630.GA15967@mars.ravnborg.org> (raw)
In-Reply-To: <20060706163728.GN26941@stusta.de>
On Thu, Jul 06, 2006 at 06:37:28PM +0200, Adrian Bunk wrote:
> Currently, using an undeclared function gives a compile warning, but it
> can lead to a nasty to debug runtime stack corruptions if the prototype
> of the function is different from what gcc guessed.
>
> With -Werror-implicit-function-declaration we are getting an immediate
> compile error instead.
This patch broke (-rc1):
sparc allnoconfig build
ia64 allnoconfig build
ppc64 allnoconfig build
x86_64 succeded an allnoconfig build
I did not try other architectures. We need to fix the allnoconfig cases
at least for the popular architectures before applying this patch
otherwise it will create too much trouble/noise.
linux-arch copied in the hope that the arch maintaines may try it out
and fix their issues.
Sam
---
Makefile | 3 ++-
drivers/input/joystick/iforce/Makefile | 2 --
2 files changed, 2 insertions(+), 3 deletions(-)
--- linux-2.6.17-mm6-full/Makefile.old 2006-07-06 12:17:02.000000000 +0200
+++ linux-2.6.17-mm6-full/Makefile 2006-07-06 12:18:52.000000000 +0200
@@ -318,7 +318,8 @@
CPPFLAGS := -D__KERNEL__ $(LINUXINCLUDE)
CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
- -fno-strict-aliasing -fno-common
+ -fno-strict-aliasing -fno-common \
+ -Werror-implicit-function-declaration
# Force gcc to behave correct even for buggy distributions
CFLAGS += $(call cc-option, -fno-stack-protector-all \
-fno-stack-protector)
--- linux-2.6.17-mm6-full/drivers/input/joystick/iforce/Makefile.old 2006-07-06 12:19:08.000000000 +0200
+++ linux-2.6.17-mm6-full/drivers/input/joystick/iforce/Makefile 2006-07-06 12:19:16.000000000 +0200
@@ -16,5 +16,3 @@
ifeq ($(CONFIG_JOYSTICK_IFORCE_USB),y)
iforce-objs += iforce-usb.o
endif
-
-EXTRA_CFLAGS = -Werror-implicit-function-declaration
next parent reply other threads:[~2006-07-07 3:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060706163728.GN26941@stusta.de>
2006-07-07 3:36 ` Sam Ravnborg [this message]
2006-07-07 5:02 ` [2.6 patch] add -Werror-implicit-function-declaration to CFLAGS Valdis.Kletnieks
2006-07-07 6:42 ` Sam Ravnborg
2006-07-07 7:49 ` Adrian Bunk
2006-07-07 7:18 ` Adrian Bunk
2006-07-07 7:49 ` Heiko Carstens
2006-07-07 9:33 ` Sam Ravnborg
2006-07-07 17:10 Luck, Tony
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=20060707033630.GA15967@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bunk@stusta.de \
--cc=davej@redhat.com \
--cc=kai@germaschewski.name \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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