From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Build failure with v3.17-rc1
Date: Thu, 21 Aug 2014 23:33:24 +0100 [thread overview]
Message-ID: <20140821223324.GM30401@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140821211100.GS11146@saruman.home>
On Thu, Aug 21, 2014 at 04:11:00PM -0500, Felipe Balbi wrote:
> Hi Russell,
>
> When running my randconfig build tests, I noticed that I had a build
> failure at arch/arm/kernel/patch.c
>
> KCONFIG_SEED=0x26B77624
> arch/arm/kernel/patch.c: In function ?__patch_text?:
> arch/arm/kernel/patch.c:35:4: error: implicit declaration of function ?__opcode_to_mem_thumb32? [-Werror=implicit-function-declaration]
> insn = __opcode_to_mem_thumb32(insn);
> ^
> cc1: some warnings being treated as errors
> make[1]: *** [arch/arm/kernel/patch.o] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make: *** [arch/arm/kernel] Error 2
> make: *** Waiting for unfinished jobs....
>
> Looking at the definition of __opcode_to_mem_thumb32 it's easy to see
> that it's not defined when ! CONFIG_CPU_ENDIAN_BE8 and that's exactly
> what I have in my generated defconfig (attached).
>
> Would below patch be the correct fix for this ?
I think you should read a bit more of the file first. In the ifdef which
starts in the context of your patch:
#ifndef CONFIG_CPU_ENDIAN_BE32
/*
* On BE32 systems, using 32-bit accesses to store Thumb instructions will not
* work in all cases, due to alignment constraints. For now, a correct
* version is not provided for BE32.
*/
#define __opcode_to_mem_thumb32(x) ___opcode_swahw32(x)
#define ___asm_opcode_to_mem_thumb32(x) ___asm_opcode_swahw32(x)
#endif
The contents of the ifdef cover the !BE32 case. It doesn't cover the BE32
case, and the BE32 case is what is being referred to in the comment.
It seems that it is intentionally not provided because it's currently
broken, and has been broken for about the last two years.
Further information can be found by looking in the git history, which
brings up commit ID 57b9da32addd. This commit text implies the need
for __opcode_to_mem_thumb32() is an error.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2014-08-21 22:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 21:11 Build failure with v3.17-rc1 Felipe Balbi
2014-08-21 22:33 ` Russell King - ARM Linux [this message]
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=20140821223324.GM30401@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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