mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: sparclinux@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.10-rc3
Date: Mon, 10 Jun 2024 09:28:25 +0200 (CEST)	[thread overview]
Message-ID: <46c5a25-ea8c-4a1-5241-df88a9848a9@linux-m68k.org> (raw)
In-Reply-To: <20240610071049.933142-1-geert@linux-m68k.org>

On Mon, 10 Jun 2024, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.10-rc3[1] to v6.10-rc2[3], the summaries are:
>  - build errors: +6/-1

   + 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+0x34), (.fixup+0x10), (.fixup+0x0), (.fixup+0x28), (.fixup+0x4), (.fixup+0x18), (.fixup+0x20), (.fixup+0x1c), (.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-gcc5/sparc-allmodconfig
sparc64-gcc13/sparc-allmodconfig

   + {standard input}: Error: pcrel too far: 1095, 1074, 1022, 1020, 1021, 1096, 1126 => 1074, 1021, 1255, 1096, 1095, 1020, 1022, 1126, 1254
   + {standard input}: Error: unknown pseudo-op: `.al':  => 1270

SH ICE crickets

> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/83a7eefedc9b56fe7bfeff13b6c7356688ffa670/ (all 138 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/c3f38fa61af77b49866b006939479069cd451173/ (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-06-10  7:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09 21:27 Linux 6.10-rc3 Linus Torvalds
2024-06-10  7:10 ` Build regressions/improvements in v6.10-rc3 Geert Uytterhoeven
2024-06-10  7:28   ` Geert Uytterhoeven [this message]
2024-06-11 17:37     ` Sam Ravnborg
2024-06-11 19:50       ` Geert Uytterhoeven
2024-06-11 20:53         ` Sam Ravnborg
2024-06-20 11:41       ` Andreas Larsson
2024-06-10 16:11 ` Linux 6.10-rc3 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=46c5a25-ea8c-4a1-5241-df88a9848a9@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@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

all inboxes | Powered by JetHome®