From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Subject: Re: Build regressions/improvements in v6.2-rc8
Date: Mon, 13 Feb 2023 11:11:50 +0100 (CET) [thread overview]
Message-ID: <7154f87-ca35-4d13-7a7c-1e29105d3b8c@linux-m68k.org> (raw)
In-Reply-To: <20230213100542.328169-1-geert@linux-m68k.org>
On Mon, 13 Feb 2023, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.2-rc8[1] to v6.2-rc7[3], the summaries are:
> - build errors: +11/-1
+ {standard input}: Error: unrecognized opcode: `dcbfl': => 5736, 4743, 4327, 4476, 4447, 5067, 4602, 5212, 5224, 4298, 5594, 4315, 5050, 5195, 4464, 5079
+ {standard input}: Error: unrecognized opcode: `dlmzb.': => 2848, 18800, 2842, 2383, 106, 2377, 3327, 112
+ {standard input}: Error: unrecognized opcode: `iccci': => 204, 163, 510
+ {standard input}: Error: unrecognized opcode: `lbarx': => 570, 196
+ {standard input}: Error: unrecognized opcode: `mbar': => 887, 558, 1172, 539, 516, 837, 1457, 1125, 815, 7523, 1100, 1385, 368, 703, 662, 468, 441, 1410
+ {standard input}: Error: unrecognized opcode: `mfdcr': => 3589, 4358, 3565, 3493, 3614, 128, 3445, 276, 3518, 3541, 3469, 4413
+ {standard input}: Error: unrecognized opcode: `mtdcr': => 265, 4402, 4430, 4375, 4388, 4347, 117, 4443
+ {standard input}: Error: unrecognized opcode: `stbcx.': => 196, 570
+ {standard input}: Error: unrecognized opcode: `tlbwe': => 475, 476, 477
powerpc-gcc11/ppc64_book3e_allmodconfig
powerpc-gcc11/powerpc-allmodconfig
powerpc-gcc11/corenet64_smp_defconfig
powerpc-gcc11/powerpc-allyesconfig
powerpc-gcc11/44x/fsp2_defconfig
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/ceaa837f96adb69c0df0397937cd74991d5d821a/ (all 152 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/4ec5183ec48656cec489c49f989c508b68b518e3/ (all 152 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
next prev parent reply other threads:[~2023-02-13 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 22:22 Linux 6.2-rc8 Linus Torvalds
2023-02-13 10:05 ` Build regressions/improvements in v6.2-rc8 Geert Uytterhoeven
2023-02-13 10:11 ` Geert Uytterhoeven [this message]
2023-02-14 0:38 ` Michael Ellerman
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=7154f87-ca35-4d13-7a7c-1e29105d3b8c@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).