public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "angelo@kernel-space.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/109133] New: Error: operands mismatch -- statement `movec %d0,%cacr' ignored
Date: Tue, 14 Mar 2023 21:08:40 +0000	[thread overview]
Message-ID: <bug-109133-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             reply	other threads:[~2023-03-14 21:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 21:08 angelo@kernel-space.org [this message]
2024-01-01 18:01 ` [Bug target/109133] " mikpelinux at gmail dot com
2024-01-01 18:44 ` schwab@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=bug-109133-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).