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: linux-bcachefs@vger.kernel.org, intel-xe@lists.freedesktop.org,
	 dri-devel@lists.freedesktop.org
Subject: Re: Build regressions/improvements in v6.11-rc2
Date: Mon, 5 Aug 2024 10:25:08 +0200 (CEST)	[thread overview]
Message-ID: <f02ec5a4-2918-24e3-8683-f965e2139830@linux-m68k.org> (raw)
In-Reply-To: <20240805080012.239408-1-geert@linux-m68k.org>

On Mon, 5 Aug 2024, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.11-rc2[1] to v6.11-rc1[3], the summaries are:
>  - build errors: +9/-4

   + /kisskb/src/fs/bcachefs/data_update.c: error: the frame size of 1032 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]:  => 338:1

m68k-gcc8/m68k-allmodconfig

   + /kisskb/src/include/linux/compiler_types.h: error: call to '__compiletime_assert_950' declared with attribute error: FIELD_GET: mask is not constant:  => 510:38
   + /kisskb/src/include/linux/compiler_types.h: error: call to '__compiletime_assert_951' declared with attribute error: FIELD_GET: mask is not constant:  => 510:38

In function 'decode_oa_format.isra.26',
     inlined from 'xe_oa_set_prop_oa_format' at /kisskb/src/drivers/gpu/drm/xe/xe_oa.c:1664:6:

powerpc-gcc5/powerpc-all{mod,yes}config
powerpc-gcc5/ppc64le_allmodconfig

Seen before, fix available

   + {standard input}: Error: displacement to undefined symbol .L142 overflows 8-bit field :  => 1070
   + {standard input}: Error: displacement to undefined symbol .L161 overflows 8-bit field :  => 1075
   + {standard input}: Error: pcrel too far: 1397 => 1059, 1254, 1060, 1061, 1255
   + {standard input}: Error: unknown pseudo-op: `.al':  => 1270
   + {standard input}: Error: unknown pseudo-op: `.l18':  => 1111
   + {standard input}: Error: unknown pseudo-op: `.siz':  => 1273

sh4-gcc13 crickets

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-08-05  8:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-04 21:00 Linux 6.11-rc2 Linus Torvalds
2024-08-05  8:00 ` Build regressions/improvements in v6.11-rc2 Geert Uytterhoeven
2024-08-05  8:25   ` Geert Uytterhoeven [this message]
2024-08-05 16:00 ` Linux 6.11-rc2 Guenter Roeck
2024-08-06  4:21   ` Guenter Roeck
2024-08-06  5:13     ` [REGRESSION] QEMU malta MIPS64 network failure (was: Re: Linux 6.11-rc2) Jiaxun Yang

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=f02ec5a4-2918-24e3-8683-f965e2139830@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-bcachefs@vger.kernel.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

all inboxes | Powered by JetHome®