linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.4-rc7
Date: Mon, 19 Jun 2023 11:10:38 +0200 (CEST)	[thread overview]
Message-ID: <8e673d4-9748-1e3c-998-346ee1742ac2@linux-m68k.org> (raw)
In-Reply-To: <20230619084641.3909582-1-geert@linux-m68k.org>

On Mon, 19 Jun 2023, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.4-rc7[1] to v6.4-rc6[3], the summaries are:
>  - build errors: +1/-5

   + {standard input}: Error: branch to a symbol in another ISA mode: 5023, 5028 => 5017, 5023, 5028, 5012

mips-gcc1[12]/micro32r2{,el}_defconfig

Not exactly a new problem, but we got two new of these while compiling
arch/mips/kernel/smp-cps.o, due to the addition of two gcc12 builds.

I could reproduce this with micro32r2_defconfig on next-20230691 using
gcc-12.3.0 from kernel.org crosstool.

In arch/mips/kernel/smp-cps.c:

     static void cps_init_secondary(void)
     {
 	    int core = cpu_core(&current_cpu_data);

 	    /* Disable MT - we only want to run 1 TC per VPE */
 	    if (cpu_has_mipsmt)
 		    dmt();

 	    ...
     }

"make arch/mips/kernel/smp-cps.s" shows cps_init_secondary() is compiled
with the following ISA settings:

         .set    nomips16
         .set    micromips

while arch/mips/include/asm/mipsmtregs.h has:

     static inline unsigned int dmt(void)
     {
 	    int res;

 	    __asm__ __volatile__(
 	    "       .set    push                                            \n"
 	    "       .set    mips32r2                                        \n"
 	    "       .set    noat                                            \n"
 	    "       .word   0x41610BC1                      # dmt $1        \n"
 	    "       ehb                                                     \n"
 	    "       move    %0, $1                                          \n"
 	    "       .set    pop                                             \n"
 	    : "=r" (res));

 	    instruction_hazard();

 	    return res;
     }

> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/45a3e24f65e90a047bef86f927ebdc4c710edaa1/ (all 160 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/858fd168a95c5b9669aac8db6c14a9aeab446375/ (151 out of 160 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-06-19  9:10 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20230619084641.3909582-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=8e673d4-9748-1e3c-998-346ee1742ac2@linux-m68k.org \
    --to=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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).