mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Valentin Schneider <vschneid@redhat.com>
Subject: Re: {standard input}:11828: Error: pcrel offset for branch to .LS005A too far (0x3e)
Date: Wed, 21 Jan 2026 16:39:42 +0100	[thread overview]
Message-ID: <aXDzPokjHlJweiBY@jlelli-thinkpadt14gen4.remote.csb> (raw)
In-Reply-To: <202601212126.OCGOmVW7-lkp@intel.com>

Hello,

On 21/01/26 21:14, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   6c790212c588fddeb0d852f2790840753bb604b1
> commit: bb4700adc3abec34c0a38b64f66258e4e233fc16 sched/deadline: Always stop dl-server before changing parameters
> date:   5 months ago
> config: csky-randconfig-r122-20260121 (https://download.01.org/0day-ci/archive/20260121/202601212126.OCGOmVW7-lkp@intel.com/config)
> compiler: csky-linux-gcc (GCC) 15.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260121/202601212126.OCGOmVW7-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202601212126.OCGOmVW7-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
>    {standard input}: Assembler messages:
> >> {standard input}:11828: Error: pcrel offset for branch to .LS005A too far (0x3e)

Thanks for the report. I was able to reproduce the issue following the
instructions provided:

  {standard input}:11828: Error: pcrel offset for branch to .LS005A too far (0x3e)
  make[5]: *** [../scripts/Makefile.build:287: kernel/sched/build_utility.o] Error 1

The failure occurs when compiling kernel/sched/build_utility.c.

I tested with several GCC versions using the same config and got
different results:

  GCC 14.2.0: builds successfully (build_utility.o created, 133KB)
  GCC 14.3.0: builds successfully (build_utility.o created, 133KB)
  GCC 15.1.0: fails with pcrel offset error at line 11797
  GCC 15.2.0: fails with pcrel offset error at line 11828 (as reported)

The error appears consistently with GCC 15.x but not with GCC 14.x when
building the same commit (bb4700adc3abec) with the provided randconfig
for csky architecture.

Interestingly, comparing the generated assembly output, GCC 15.2
produces approximately ~5% more code than GCC 14.3 for build_utility.c
(912KB vs 868KB assembly, 25479 vs 24356 lines).

I'm not sure whether this indicates a GCC 15 code generation issue for
csky, something specific about this randconfig that triggers a boundary
condition, or if there's an actual code issue I'm not seeing. The code
changes in the commit are minimal (removing a condition check before
calling dl_server_stop) and seem straightforward.

Is this maybe a known compiler issue?

Thanks,
Juri


      reply	other threads:[~2026-01-21 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-21 13:14 kernel test robot
2026-01-21 15:39 ` Juri Lelli [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=aXDzPokjHlJweiBY@jlelli-thinkpadt14gen4.remote.csb \
    --to=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=vschneid@redhat.com \
    /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

all inboxes | Powered by JetHome®