From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: linux-sh@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.6-rc6
Date: Mon, 16 Oct 2023 09:26:43 +0200 (CEST) [thread overview]
Message-ID: <f895f03-9661-9bd0-c112-84bc73df5057@linux-m68k.org> (raw)
In-Reply-To: <20231016070610.677494-1-geert@linux-m68k.org>
On Mon, 16 Oct 2023, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.6-rc6[1] to v6.6-rc5[3], the summaries are:
> - build errors: +14/-0
+ {standard input}: Error: displacement to undefined symbol .L100 overflows 12-bit field: => 602
+ {standard input}: Error: displacement to undefined symbol .L101 overflows 12-bit field: => 607
+ {standard input}: Error: displacement to undefined symbol .L102 overflows 8-bit field : => 588
+ {standard input}: Error: displacement to undefined symbol .L103 overflows 8-bit field : => 593
+ {standard input}: Error: displacement to undefined symbol .L149 overflows 8-bit field : => 606
+ {standard input}: Error: displacement to undefined symbol .L72 overflows 12-bit field: => 589
+ {standard input}: Error: displacement to undefined symbol .L73 overflows 12-bit field: => 594
+ {standard input}: Error: displacement to undefined symbol .L73 overflows 8-bit field : => 580
+ {standard input}: Error: displacement to undefined symbol .L74 overflows 8-bit field : => 585
+ {standard input}: Error: displacement to undefined symbol .L77 overflows 8-bit field : => 607
+ {standard input}: Error: displacement to undefined symbol .L78 overflows 8-bit field : => 610
sh4-gcc11/sh-all{mod,yes}config
+ {standard input}: Error: missing operand: => 612
sh4-gcc11/sh-allyesconfig
+ {standard input}: Error: pcrel too far: 933, 934 => 598, 572, 593, 936, 604, 937, 577, 599
sh4-gcc12/sh-allmodconfig
sh4-gcc11/sh-all{mod,yes}config
+ {standard input}: Error: unknown pseudo-op: `.': => 609
sh4-gcc11/sh-allmodconfig
All of the above are caused by ICEs, so nihil novum sub sole.
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/58720809f52779dc0f08e53e54b014209d13eebb/ (237 out of 239 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/94f6f0550c625fab1f373bb86a6669b45e9748b3/ (all 239 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
parent reply other threads:[~2023-10-16 7:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20231016070610.677494-1-geert@linux-m68k.org>]
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=f895f03-9661-9bd0-c112-84bc73df5057@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@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 read-only IMAP folder(s) and NNTP newsgroup(s).