From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: kprobes-test: Fix compile error "bad immediate value for offset"
Date: Fri, 26 Sep 2014 16:19:48 +0100 [thread overview]
Message-ID: <20140926151947.GV5182@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1411743864.1529.36.camel@linaro1.home>
On Fri, Sep 26, 2014 at 04:04:24PM +0100, Jon Medhurst (Tixy) wrote:
> When compiling kprobes-test-arm.c the following error has been observed
>
> /tmp/ccoT403o.s:21439: Error: bad immediate value for offset (4168)
>
> This is caused by the compiler spilling it's literal pool too far away
> from the site which is trying to reference it with a PC relative load.
> This arises because the compiler is underestimating the size of the
> inline assembler code present, which apparently it approximates as 4
> bytes per line or instruction.
>
> We fix this problem by moving the operations which generate more than
> 4 bytes out of the text section. Specifically, moving the .ascii
> directives to the .rodata section.
>
> Signed-off-by: Jon Medhurst <tixy@linaro.org>
> ---
>
> Russell, OK to add your 'reported-by' here (or should it be Olof)?
I suspect it should be Olof - I'm just the middle man, spotting errors
in Olof's build results... though it did help that it was my for-next
branch which was being built.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-09-26 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 15:04 [PATCH] arm: kprobes-test: Fix compile error "bad immediate value for offset" Jon Medhurst (Tixy)
2014-09-26 15:19 ` Russell King - ARM Linux [this message]
2014-09-30 9:33 ` Jon Medhurst (Tixy)
2014-09-30 9:56 ` Russell King - ARM Linux
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=20140926151947.GV5182@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;
as well as URLs for NNTP newsgroup(s).