[Bug libgcc/109133] New: Error: operands mismatch -- statement `movec %d0,%cacr' ignored

[Bug libgcc/109133] New: Error: operands mismatch -- statement `movec %d0,%cacr' ignored

[angelo@kernel-space.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109133

            Bug ID: 109133
           Summary: Error: operands mismatch -- statement `movec
                    %d0,%cacr' ignored
           Product: gcc
           Version: 12.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcc
          Assignee: unassigned at gcc dot gnu.org
          Reporter: angelo@kernel-space.org
  Target Milestone: ---

Hi,

not clear if this may be related to binutils, i using gcc btw.
I am just using for test

-march=isac

on mcf54415, that should work. But i am observing this error:


  /opt/toolchains/m68k/gcc-12.2.0-nolibc/m68k-linux/bin/m68k-linux-gcc
-Wp,-MD,arch/m68k/lib/.interrupts.o.d -nostdinc -isystem
/opt/toolchains/m68k/gcc-12.2.0-nolibc/m68k-linux/bin/../lib/gcc/m68k-linux/12.2.0/include
-Iinclude   -I./arch/m68k/include -include ./include/linux/kconfig.h
-D__KERNEL__ -D__UBOOT__ -Wall -Wstrict-prototypes -Wno-format-security
-fno-builtin -ffreestanding -std=gnu11 -fshort-wchar -fno-strict-aliasing
-fno-PIE -Os -fno-stack-protector -fno-delete-null-pointer-checks
-Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds
-Wno-array-bounds -Wno-stringop-overflow -Wno-maybe-uninitialized
-fmacro-prefix-map=./= -gdwarf-4 -fstack-usage -Wno-format-nonliteral
-Wno-address-of-packed-member -Wno-unused-but-set-variable -Werror=date-time
-Wno-packed-not-aligned -D__M68K__ -ffunction-sections -fdata-sections
-ffixed-d7 -msep-data -pipe -march=isac -fPIC   
-DKBUILD_BASENAME='"interrupts"'  -DKBUILD_MODNAME='"interrupts"' -c -o
arch/m68k/lib/interrupts.o arch/m68k/lib/interrupts.c
{standard input}: Assembler messages:
{standard input}:103: Error: operands mismatch -- statement `movec %d0,%cacr'
ignored
{standard input}:136: Error: operands mismatch -- statement `movec %d0,%acr2'
ignored
{standard input}:139: Error: operands mismatch -- statement `movec %d0,%acr3'
ignored
{standard input}:139: Error: operands mismatch -- statement `movec %d0,%acr6'
ignored
{standard input}:139: Error: operands mismatch -- statement `movec %d0,%acr7'
ignored
{standard input}:142: Error: operands mismatch -- statement `movec %d0,%cacr'
ignored
{standard input}:174: Error: operands mismatch -- statement `movec %d0,%acr2'
ignored
{standard input}:174: Error: operands mismatch -- statement `movec %d0,%acr3'
ignored
{standard input}:174: Error: operands mismatch -- statement `movec %d0,%acr6'
ignored
{standard input}:174: Error: operands mismatch -- statement `movec %d0,%acr7'
ignored

movec is isac, so it should be legal.

If i use -mcpu=54418 in place of -march=isac, i can compile.

Regards,
angelo

[Bug target/109133] Error: operands mismatch -- statement `movec %d0,%cacr' ignored

[mikpelinux at gmail dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109133

Mikael Pettersson <mikpelinux at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mikpelinux at gmail dot com

--- Comment #1 from Mikael Pettersson <mikpelinux at gmail dot com> ---
Looks like either a problem in gas, or the gcc driver not passing appropriate
options to gas. We need a standalone test case, and please indicate exactly
what versions of gcc and binutils you're using and how they were configured and
built.

[Bug target/109133] Error: operands mismatch -- statement `movec %d0,%cacr' ignored

[schwab@linux-m68k.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109133

Andreas Schwab <schwab@linux-m68k.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #2 from Andreas Schwab <schwab@linux-m68k.org> ---
The available control registers are dependent on the particular device, a
generic setting like isac does not include any.