From: Ingo Molnar <mingo@elte.hu>
To: Roland Dreier <rdreier@cisco.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
David Howells <dhowells@redhat.com>
Subject: Re: [announce] new tree: "fix all build warnings, on all configs"
Date: Fri, 17 Oct 2008 21:12:02 +0200 [thread overview]
Message-ID: <20081017191202.GA5396@elte.hu> (raw)
In-Reply-To: <adatzbbrrcf.fsf@cisco.com>
* Roland Dreier <rdreier@cisco.com> wrote:
> However I worry about warnings produced by gcc bugs forcing us to
> tinker with correct code. Maybe it just makes sense to wait and see
> if we ever hit a case where a gcc bug forces us to make too many
> stupid changes, and figure out what to do if and when that happens.
i certainly have a found a couple of such cases, see tip/warnings/ugly -
for example see the one below where gcc is not able to see through type
width.
the threshold i'm using is: "does the code get worse". Another question
is the rate of really ugly patches. Had i ended up with a lot of them
i'd be worried - but right now they are in the low single digits, for a
full 9 MLOC kernel - which seems manageable.
the drivers/net/mlx4/mcg.c commit you pointed out is one of the very few
borderline cases: the code gets neither better, nor worse. If you look
at the totality of fixes they are not common at all. (and almost by
definition the 100-200 unfixed warnings that we have piled up in -git
are the _problematic_ cases - clear-cut cases tend to be fixed.)
Ingo
------------->
>From fbf03326a16b29f8d34a5a3883a267bac4d38fc2 Mon Sep 17 00:00:00 2001
From: Ingo Molnar <mingo@elte.hu>
Date: Wed, 27 Aug 2008 12:44:00 +0200
Subject: [PATCH] hack, workaround for warning drivers/acpi/tables/tbfadt.c
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
ugly workaround for this warning:
drivers/acpi/tables/tbfadt.c: In function ‘acpi_tb_create_local_fadt’:
include/asm/string_32.h:75: warning: array subscript is above array bounds
gcc 4.3.1 20080801 (Red Hat 4.3.1-6)
its array checks are borked. Switch the string_32.h code to short instead.
NOT-Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
include/asm-x86/string_32.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/asm-x86/string_32.h b/include/asm-x86/string_32.h
index 487843e..419ab10 100644
--- a/include/asm-x86/string_32.h
+++ b/include/asm-x86/string_32.h
@@ -72,7 +72,7 @@ static __always_inline void *__constant_memcpy(void *to, const void *from,
return to;
case 5:
*(int *)to = *(int *)from;
- *((char *)to + 4) = *((char *)from + 4);
+ *((short *)to + 3) = *((short *)from + 3);
return to;
case 6:
*(int *)to = *(int *)from;
next prev parent reply other threads:[~2008-10-17 19:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 17:11 [announce] new tree: "fix all build warnings, on all configs" Ingo Molnar
2008-10-17 17:59 ` Roland Dreier
2008-10-17 18:05 ` Ingo Molnar
2008-10-17 18:47 ` Roland Dreier
2008-10-17 19:12 ` Ingo Molnar [this message]
2008-10-17 19:36 ` Roland Dreier
2008-10-18 8:22 ` Ingo Molnar
2008-10-20 16:37 ` Linus Torvalds
2008-10-20 16:49 ` H. Peter Anvin
2008-10-20 16:57 ` Linus Torvalds
2008-10-20 19:21 ` Ingo Molnar
2008-10-21 6:41 ` Jörn Engel
2008-10-22 9:47 ` Ingo Molnar
2008-10-22 10:10 ` Jörn Engel
2008-10-18 7:43 ` Andi Kleen
2008-10-21 10:30 ` [announce] new tree: "fix all build warnings, on all configs" II Andi Kleen
2008-10-21 11:17 ` [announce] new tree: "fix all build warnings, on all configs" Ingo Molnar
2008-10-21 12:07 ` Andi Kleen
2008-10-21 19:39 ` Rafael J. Wysocki
2008-10-21 19:37 ` Rafael J. Wysocki
2008-10-22 4:11 ` Len Brown
2008-10-22 12:23 ` [PATCH] ACPI suspend: Fix CONFIG_ACPI_SLEEP dependence and some compilation warnings (was: Re: [announce] new tree: "fix all build warnings, on all configs") Rafael J. Wysocki
2008-10-22 18:58 ` Len Brown
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=20081017191202.GA5396@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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