public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/64405] New: [arm] Invalid codegenaration for ARMv3 and ARMv2
@ 2014-12-25 14:36 Sergey.Belyashov at gmail dot com
  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
  0 siblings, 2 replies; 3+ messages in thread
From: Sergey.Belyashov at gmail dot com @ 2014-12-25 14:36 UTC (permalink / raw)
  To: gcc-bugs

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug target/64405] [arm] Invalid codegenaration for ARMv3 and ARMv2
  2014-12-25 14:36 [Bug target/64405] New: [arm] Invalid codegenaration for ARMv3 and ARMv2 Sergey.Belyashov at gmail dot com
@ 2014-12-25 14:47 ` Sergey.Belyashov at gmail dot com
  2021-07-21  5:22 ` pinskia at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: Sergey.Belyashov at gmail dot com @ 2014-12-25 14:47 UTC (permalink / raw)
  To: gcc-bugs

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

Sergey Belyashov <Sergey.Belyashov at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |ARMv4
      Known to fail|                            |4.8.4

--- Comment #1 from Sergey Belyashov <Sergey.Belyashov at gmail dot com> ---
answer about GAS:
https://lists.gnu.org/archive/html/bug-binutils/2014-12/msg00145.html


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug target/64405] [arm] Invalid codegenaration for ARMv3 and ARMv2
  2014-12-25 14:36 [Bug target/64405] New: [arm] Invalid codegenaration for ARMv3 and ARMv2 Sergey.Belyashov at gmail dot com
  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
  1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-07-21  5:22 UTC (permalink / raw)
  To: gcc-bugs

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |9.0
         Resolution|---                         |WONTFIX
             Status|NEW                         |RESOLVED

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
ARMv3/ARMv2 support was removed in GCC 9+ (r9-404). So closing as won't fix.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-07-21  5:22 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-25 14:36 [Bug target/64405] New: [arm] Invalid codegenaration for ARMv3 and ARMv2 Sergey.Belyashov at gmail dot com
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

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).