Re: compile time warnings

[Ingo Brueckl]

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...@xxxxxxxxx, but is still
unfixed.

Here is what linuxtwid...@xxxxxxxxx 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.)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/