public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Sergey.Belyashov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64405] New: [arm] Invalid codegenaration for ARMv3 and ARMv2
Date: Thu, 25 Dec 2014 14:36:00 -0000	[thread overview]
Message-ID: <bug-64405-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 64405
           Summary: [arm] Invalid codegenaration for ARMv3 and ARMv2
           Product: gcc
           Version: 4.8.5
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: Sergey.Belyashov at gmail dot com

I try to compile program for ARMv3 or ARMv2 CPU target using GCC (4.8.x). It
produces assembler code with BX LR instructions (return from function) which
GAS (2.23.2) cannot compile:
   Error: selected processor does not support ARM mode `bx lr'
It is work for ARMv4 mode and greater (ARMv4 has no BX <reg> instruction
support, but GAS compiles it as MOV PC,<reg>).

As I know BX <reg> is strongly recommended to be used instead of MOV PC,<reg>
by the ARM architecture manual (section A.4.1.1) but GAS developers says, that
it is GCC bug.

GAS mail archive:
https://lists.gnu.org/archive/html/bug-binutils/2014-10/msg00017.html


             reply	other threads:[~2014-12-25 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-25 14:36 Sergey.Belyashov at gmail dot com [this message]
2014-12-25 14:47 ` [Bug target/64405] " Sergey.Belyashov at gmail dot com
2021-07-21  5:22 ` pinskia 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-64405-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).