public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64461] New: bad assembly generated for Coldfire targets
Date: Wed, 31 Dec 2014 20:24:00 -0000	[thread overview]
Message-ID: <bug-64461-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 64461
           Summary: bad assembly generated for Coldfire targets
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: joel at gcc dot gnu.org

Created attachment 34368
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34368&action=edit
Preprocessed RTEMS source which produces the error

Fails at -O1, -O2, and -Os. All RTEMS Coldfire BSPs appear to be failing to
build. I have not looked through all build logs yet to give a complete list of
CPU models impacted but all are Coldfires. For sure, 5235 and 5282 do this.

$ m68k-rtems4.11-gcc --versionm68k-rtems4.11-gcc (GCC) 5.0.0 20141230
(experimental)


$ m68k-rtems4.11-gcc -mcpu=5235 -Os -c coldfire.c 
/tmp/ccrrBmOJ.s: Assembler messages:
/tmp/ccrrBmOJ.s:82: Error: operands mismatch -- statement `move.b
3(%a5),3(%a1,%d0.l)' ignored
/tmp/ccrrBmOJ.s:977: Error: operands mismatch -- statement `move.b
-1(%fp),3(%a0,%d2.l)' ignored
/tmp/ccrrBmOJ.s:1055: Error: operands mismatch -- statement `move.b
-5(%fp),3(%a0,%d3.l)' ignored


             reply	other threads:[~2014-12-31 20:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-31 20:24 joel at gcc dot gnu.org [this message]
2015-01-02 20:37 ` [Bug target/64461] " joel at gcc dot gnu.org
2015-01-02 21:16 ` joel at gcc dot gnu.org
2015-01-02 22:29 ` schwab@linux-m68k.org
2015-01-02 22:35 ` schwab@linux-m68k.org
2015-01-02 22:48 ` joel at gcc dot gnu.org
2015-01-12 20:20 ` law at gcc dot gnu.org
2015-01-12 20:21 ` law at redhat dot com
2015-01-12 22:09 ` joel at gcc dot gnu.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-64461-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).