From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Finn Thain <fthain@linux-m68k.org>, linux-m68k@lists.linux-m68k.org
Subject: Re: Build issue "Error: operands mismatch -- statement `movec %d2,%caar' ignored" on m68k
Date: Mon, 30 Dec 2024 10:35:52 +0100 [thread overview]
Message-ID: <20241230103552.61b67498@windsurf> (raw)
In-Reply-To: <CAMuHMdWmYc4=-ZbFoNrD=2CjucxdUSqhfufJZ_UkL+wvun_jcg@mail.gmail.com>
Hello Geert,
On Mon, 30 Dec 2024 09:53:29 +0100
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > /usr/libexec/gcc/m68k-unknown-linux-musl/as -v -mcpu=68020 --pcrel -o a.o a.s
>
> Thanks, so it fails when -mcpu=68040 is passed to the assembler.
>
> Oh, I misread "caar" as "cacr". The latter exists on MC68040, the
> former does not. However, that doesn't explain the failures for pflusha,
> which is supported on 68040.
>
> After disabling CONFIG_680[236]0 in the kernel config, I can build
> it fine using the buildroot toolchain.
>
> Conclusion: make sure your toolchain supports (a superset of) the
> CPUs supported by your kernel config.
Thanks for the investigation. How should the toolchain be configured to
s upport multiple m68k CPUs? My understanding was that when you
configure gcc with --with-cpu=<something>, it means gcc will by default
emit code for <something>, but it can always be overridden when running
gcc using -mcpu=<somethingelse>.
How can one build this kernel/sys_m68k.c file if it uses instructions
that are mutually incompatible on different m68k cores?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
next prev parent reply other threads:[~2024-12-30 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-29 12:48 Build issue "Error: operands mismatch -- statement `movec %d2,%caar' ignored" on m68k Thomas Petazzoni
2024-12-29 14:23 ` Geert Uytterhoeven
2024-12-30 8:30 ` Finn Thain
2024-12-30 8:53 ` Geert Uytterhoeven
2024-12-30 9:35 ` Thomas Petazzoni [this message]
2024-12-30 9:57 ` Geert Uytterhoeven
2024-12-30 11:22 ` Andreas Schwab
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=20241230103552.61b67498@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.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 NNTP newsgroup(s).