From: Feng Tang <feng.tang@intel.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [linux-next:master 3665/11714] {standard input}:2644: Error: pcrel offset for branch to .LS0015 too far (0x3e)
Date: Tue, 22 Jun 2021 17:48:18 +0800 [thread overview]
Message-ID: <20210622094818.GA67867@shbuild999.sh.intel.com> (raw)
In-Reply-To: <202106220959.QA9KOJ3Q-lkp@intel.com>
On Tue, Jun 22, 2021 at 09:49:05AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 889bab4c367a0ef58208fd80fafa74bb6e2dca26
> commit: cf536e185869d4815d506e777bcca6edd9966a6e [3665/11714] Makefile: extend 32B aligned debug option to 64B aligned
> config: csky-randconfig-c024-20210622 (attached as .config)
> compiler: csky-linux-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=cf536e185869d4815d506e777bcca6edd9966a6e
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout cf536e185869d4815d506e777bcca6edd9966a6e
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=csky
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> {standard input}: Assembler messages:
> >> {standard input}:2644: Error: pcrel offset for branch to .LS0015 too far (0x3e)
> {standard input}:2653: Error: pcrel offset for branch to .LS0015 too far (0x34)
> {standard input}:2659: Error: pcrel offset for branch to .LS0015 too far (0x2c)
Thanks for the report.
I just reproduced the issue locally, with similar log:
CC drivers/target/target_core_sbc.o
{standard input}: Assembler messages:
{standard input}:2644: Error: pcrel offset for branch to .LS0015 too far (0x3e)
{standard input}:2653: Error: pcrel offset for branch to .LS0015 too far (0x34)
{standard input}:2659: Error: pcrel offset for branch to .LS0015 too far (0x2c)
make[2]: *** [scripts/Makefile.build:272: drivers/target/target_core_sbc.o] Error 1
m
And when I changed the function align option from 64 to 32, the
compilation did pass, so this looks to be related with the alignment
option.
I'm very familiar with compiler, and will try to check more.
I know it works on x86_64, but don't know how about other
architectures, and if 'csky' is the only not working one, one
workaround I can think of is to add kconfig dependency for !csky
Thanks,
Feng
next prev parent reply other threads:[~2021-06-22 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 1:49 [linux-next:master 3665/11714] {standard input}:2644: Error: pcrel offset for branch to .LS0015 too far (0x3e) kernel test robot
2021-06-22 9:48 ` Feng Tang [this message]
2021-06-22 9:56 ` Feng Tang
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=20210622094818.GA67867@shbuild999.sh.intel.com \
--to=feng.tang@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=masahiroy@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 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).