From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
kbuild-all@01.org
Subject: Re: [next:master 452/458] undefined reference to `__bad_size_call_parameter'
Date: Thu, 6 Mar 2014 13:18:35 -0800 [thread overview]
Message-ID: <20140306131835.543007307bf38e8986f1229c@linux-foundation.org> (raw)
In-Reply-To: <53188aab.D8+W+0kHpmaV0uFd%fengguang.wu@intel.com>
On Thu, 06 Mar 2014 22:48:11 +0800 kbuild test robot <fengguang.wu@intel.com> wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 0ffb2fe7b9c30082876fa3a17da018bf0632cf03
> commit: 3b0fc5a9f85472be761e51de110e0aa8d15e7f41 [452/458] sh: replace __get_cpu_var uses
> config: make ARCH=sh r7785rp_defconfig
>
> All error/warnings:
>
> arch/sh/kernel/built-in.o: In function `kprobe_exceptions_notify':
> >> (.kprobes.text+0x8c8): undefined reference to `__bad_size_call_parameter'
This has me stumped - the same code
p = __this_cpu_read(current_kprobe);
works OK elsewhere in that file. I'm suspecting a miscompile - it's
not unknown for gcc to screw up when we use this trick.
I can reproduce it with gcc-3.4.5 for sh.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-03-06 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 14:48 kbuild test robot
2014-03-06 21:18 ` Andrew Morton [this message]
2014-03-07 17:07 ` Christoph Lameter
2014-03-07 21:00 ` Andrew Morton
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=20140306131835.543007307bf38e8986f1229c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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