From: ib@wupperonline.de (Ingo Brueckl)
To: linux-kernel@vger.kernel.org
Subject: Re: compile time warnings
Date: Fri, 02 Jan 2009 03:48:00 +0100 [thread overview]
Message-ID: <495d7b8d@wupperonline.de> (raw)
In-Reply-To: <495d3100@wupperonline.de>
What we have so far:
arch/x86/kernel/setup.c:742: warning: 'dmi_low_memory_corruption'
is already fixed in the git tree.
arch/x86/mm/init_32.c:515: warning: unused variable 'pgd_base'
could be fixed with Jespers patch (which I like best).
WARNING: modpost: Found 1 section mismatch(es).
which is (with CONFIG_DEBUG_SECTION_MISMATCH=y):
WARNING: vmlinux.o(.cpuinit.data+0x0): Section mismatch in reference from
the variable initial_code to the function .init.text:i386_start_kernel()
The variable __cpuinitdata initial_code references a function __init
i386_start_kernel(). If i386_start_kernel is only used by initial_code then
annotate i386_start_kernel with a matching annotation.
was already noticed some time ago by linuxtwid...@gmail.com, but is still
unfixed.
Here is what linuxtwid...@gmail.com suggested:
--- linux-2.6.27.1/arch/x86/kernel/head_32.S 2008-10-16 00:49:00.000000000 -0500
+++ linux-2.6.27.1-test/arch/x86/kernel/head_32.S 2008-10-16 01:45:10.000000000 -0500
@@ -600,6 +600,7 @@ ignore_int:
.section .cpuinit.data,"wa"
.align 4
+__REFDATA
ENTRY(initial_code)
.long i386_start_kernel
The remaining
/usr/src/linux/arch/x86/include/asm/string_32.h:75: warning: array subscript is above array bounds
is very strange and a mystery to me. (There were already reports on that
issue which seem to point to a gcc bug.)
next prev parent reply other threads:[~2009-01-02 2:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 21:13 compile time warnings Ingo Brueckl
2009-01-01 22:52 ` Jesper Juhl
2009-01-02 1:35 ` Tom Spink
2009-01-02 1:39 ` Harvey Harrison
2009-01-02 2:07 ` Jesper Juhl
2009-01-02 9:57 ` Ingo Molnar
2009-01-02 12:53 ` [PATCH] " Ingo Brueckl
2009-01-02 13:01 ` Ingo Molnar
2009-01-02 13:42 ` Ingo Brueckl
2009-01-02 14:42 ` Ingo Molnar
2009-01-02 16:07 ` Jesper Juhl
2009-01-02 16:10 ` Jesper Juhl
2009-01-02 2:48 ` Ingo Brueckl [this message]
2009-01-02 20:03 ` Robert Hancock
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=495d7b8d@wupperonline.de \
--to=ib@wupperonline.de \
--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