From: Vipul Pandya <vipul@chelsio.com>
To: David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: You have to fix this
Date: Wed, 03 Oct 2012 15:42:05 +0530 [thread overview]
Message-ID: <506C0F75.4080309@chelsio.com> (raw)
In-Reply-To: <20120928.134313.2263654281720915031.davem@davemloft.net>
On 28-09-2012 23:13, David Miller wrote:
> From: Vipul Pandya <vipul@chelsio.com>
> Date: Fri, 28 Sep 2012 17:29:22 +0530
>
>> Please let me know how else would I get above warning message?
>
> Maybe your compiler is too old. Does -Wframe-larger-than= show up in your
> build logs with "make V=1"?
>
I am using gcc version 4.4.4 20100726. Yes -Wframe-larger-than=2048 does
show up in my build logs as shown below:
===
gcc -Wp,-MD,arch/x86/kernel/.hw_breakpoint.o.d -nostdinc -isystem
/usr/lib/gcc/x86_64-redhat-linux/4.4.4/include
-I/root/git_kernel_tree/net-next/arch/x86/include
-Iarch/x86/include/generated -Iinclude -include
/root/git_kernel_tree/net-next/include/linux/kconfig.h -D__KERNEL__
-Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing
-fno-common -Werror-implicit-function-declaration -Wno-format-security
-fno-delete-null-pointer-checks -O2 -m64 -mtune=generic -mno-red-zone
-mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args
-DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1
-DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_AVX=1 -pipe
-Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx
-mno-sse2 -mno-3dnow -mno-avx -Wframe-larger-than=2048
-fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer
-Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow
-fconserve-stack -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=#s"
-D"KBUILD_BASENAME=KBUILD_STR(hw_breakpoint)"
-D"KBUILD_MODNAME=KBUILD_STR(hw_breakpoint)" -c -o
arch/x86/kernel/hw_breakpoint.o arch/x86/kernel/hw_breakpoint.c
===
next prev parent reply other threads:[~2012-10-03 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 22:34 You have to fix this David Miller
2012-09-28 11:59 ` Vipul Pandya
2012-09-28 17:43 ` David Miller
2012-10-03 10:12 ` Vipul Pandya [this message]
2012-10-03 21:17 ` Randy Dunlap
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=506C0F75.4080309@chelsio.com \
--to=vipul@chelsio.com \
--cc=davem@davemloft.net \
--cc=netdev@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 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.