Linux-sh Archive mirror
 help / color / mirror / Atom feed
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.7-rc4
Date: Mon, 4 Dec 2023 08:48:39 +0100 (CET)	[thread overview]
Message-ID: <beef78b-ca1e-6f3-5bbb-b9e38e3a57b8@linux-m68k.org> (raw)
In-Reply-To: <20231203200454.396428-1-geert@linux-m68k.org>

On Sun, 3 Dec 2023, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.7-rc4[1] to v6.7-rc3[3], the summaries are:
>  - build errors: +6/-5

   + {standard input}: Error: displacement to undefined symbol .L105 overflows 8-bit field :  => 593
   + {standard input}: Error: displacement to undefined symbol .L140 overflows 8-bit field :  => 606
   + {standard input}: Error: displacement to undefined symbol .L76 overflows 12-bit field:  => 594
   + {standard input}: Error: displacement to undefined symbol .L97 overflows 12-bit field:  => 607
   + {standard input}: Error: pcrel too far: 610, 572, 590, 599, 593, 596, 569 => 596, 569, 593, 598, 610, 604, 572, 590, 599, 577
   + {standard input}: Error: unknown pseudo-op: `.l':  => 609

SH ICE crickets.

> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/33cc938e65a98f1d29d0a18403dbbee050dcad9a/ (all 239 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/2cc14f52aeb78ce3f29677c2de1f06c0e91471ab/ (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

           reply	other threads:[~2023-12-04  7:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20231203200454.396428-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=beef78b-ca1e-6f3-5bbb-b9e38e3a57b8@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).