From: vibi sreenivasan <vibi_sreenivasan@cms.com>
To: linux-next@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Warnings while compiling for i386
Date: Fri, 11 Jul 2008 15:38:56 +0530 [thread overview]
Message-ID: <1215770936.2995.27.camel@localhost.localdomain> (raw)
hello ,
I am getting alot of warnings while compiling for i386 architecture.
i am using default configuration for i386 & my compiler version is
4.1.1
following are warnings
arch/x86/kernel/smpboot.c: In function ‘do_boot_cpu’:
arch/x86/kernel/smpboot.c:943: warning: label ‘restore_state’ defined
but not used
*
*
arch/x86/mm/pgtable.c: In function ‘pgd_mop_up_pmds’:
arch/x86/mm/pgtable.c:194: warning: unused variable ‘pmd’
CC arch/x86/mm/pgtable_32.o
arch/x86/mm/pgtable_32.c:144: warning: ‘fixmaps’ defined but not used
*
*
kernel/sched.c:7743: warning: initialization from incompatible pointer
type
kernel/sched.c:7743: warning: initialization from incompatible pointer
type
*
*
sound/core/pcm_native.c: In function ‘snd_pcm_fasync’:
sound/core/pcm_native.c:3262: warning: label ‘out’ defined but not used
*
*
WARNING: modpost: Found 6 section mismatch(es).
*
*
RELOCS arch/x86/boot/compressed/vmlinux.relocs
WARNING: Absolute relocations present
Offset Info Type Sym.Value Sym.Name
c103405d 00807601 R_386_32 c1357371 __start_notes
c13627a8 0098e101 R_386_32 c14a5efc __start___kcrctab
c13627bc 00984101 R_386_32 c14a5efc __start___kcrctab_gpl
c13627c8 00797001 R_386_32 c14a5efc __start___ksymtab_gpl_future
c13627cc 0082ba01 R_386_32 c14a5efc __stop___ksymtab_gpl_future
c13627d0 00802801 R_386_32 c14a5efc __start___kcrctab_gpl_future
c153c1fe 008e7401 R_386_32 c1357371 __stop_notes
c153c204 00807601 R_386_32 c1357371 __start_notes
Thanks & Regards
vibi sreenivasan
next reply other threads:[~2008-07-11 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 10:08 vibi sreenivasan [this message]
2008-07-11 10:21 ` Warnings while compiling for i386 Stephen Rothwell
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=1215770936.2995.27.camel@localhost.localdomain \
--to=vibi_sreenivasan@cms.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.