linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.9-rc6
Date: Mon, 29 Apr 2024 10:36:14 +0200 (CEST)	[thread overview]
Message-ID: <21838384-b8c0-e38e-691d-c2cf6b87fa@linux-m68k.org> (raw)
In-Reply-To: <20240429083040.4015092-1-geert@linux-m68k.org>

On Mon, 29 Apr 2024, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.9-rc6[1] to v6.9-rc5[3], the summaries are:
>  - build errors: +11/-7

   + error: arch/sparc/kernel/process_32.o: relocation truncated to fit: R_SPARC_WDISP22 against `.text':  => (.fixup+0x4), (.fixup+0xc)
   + error: arch/sparc/kernel/signal_32.o: relocation truncated to fit: R_SPARC_WDISP22 against `.text':  => (.fixup+0x0), (.fixup+0x18), (.fixup+0x10), (.fixup+0x20), (.fixup+0x8)
   + error: relocation truncated to fit: R_SPARC_WDISP22 against `.init.text':  => (.head.text+0x5040), (.head.text+0x5100)
   + error: relocation truncated to fit: R_SPARC_WDISP22 against symbol `leon_smp_cpu_startup' defined in .text section in arch/sparc/kernel/trampoline_32.o:  => (.init.text+0xa4)

sparc64-gcc13/sparc-allmodconfig (seen before)

   + {standard input}: Error: displacement to undefined symbol .L107 overflows 12-bit field:  => 758
   + {standard input}: Error: displacement to undefined symbol .L119 overflows 12-bit field:  => 761
   + {standard input}: Error: displacement to undefined symbol .L121 overflows 12-bit field:  => 729
   + {standard input}: Error: displacement to undefined symbol .L96 overflows 12-bit field:  => 791, 716, 852, 696, 943, 775, 800, 739, 916
   + {standard input}: Error: displacement to undefined symbol .L96 overflows 8-bit field :  => 932, 870

sh4-gcc13/sh-allyesconfig (ICE crickets)

   + {standard input}: Error: pcrel too far: 561, 552, 588, 563, 545, 570, 554, 579, 543, 581, 590, 572 => 833, 878, 557, 720, 550, 884, 566, 586, 933, 575, 779, 806, 877, 925, 568, 856, 765, 888, 844, 827, 584, 559, 548, 804, 909, 927, 679, 593, 858, 700, 843, 920, 595, 828, 706, 577

sh4-gcc13/sh-all{mod,yes}config (ICE crickets)

   + {standard input}: Error: unknown pseudo-op: `.cfi_def_cfa_off':  => 609

sh4-gcc13/sh-allmodconfig (ICE crickets)

> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/e67572cd2204894179d89bd7b984072f19313b03/ (all 138 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/ed30a4a51bb196781c8058073ea720133a65596f/ (all 138 configs)

Gr{oetje,eeting}s,

 						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
 							    -- Linus Torvalds

  reply	other threads:[~2024-04-29  8:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-28 20:58 Linux 6.9-rc6 Linus Torvalds
2024-04-29  8:30 ` Build regressions/improvements in v6.9-rc6 Geert Uytterhoeven
2024-04-29  8:36   ` Geert Uytterhoeven [this message]
2024-04-30 18:40 ` Linux 6.9-rc6 Guenter Roeck

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=21838384-b8c0-e38e-691d-c2cf6b87fa@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.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).