public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64224] New: [ARM] -mapcs -marm uses deprecated forms (as of ARMv7-A) of LDM in epilogues
Date: Mon, 08 Dec 2014 14:43:00 -0000	[thread overview]
Message-ID: <bug-64224-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 64224
           Summary: [ARM] -mapcs -marm uses deprecated forms (as of
                    ARMv7-A) of LDM in epilogues
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: ktkachov at gcc dot gnu.org
          Reporter: ktkachov at gcc dot gnu.org
            Target: arm*

The ARMv7-A specification says on the load-multiple (LDM) instruction:
"The SP can be in the list. However, ARM deprecates using these instructions
with SP in the list."

and

"ARM deprecates using these instructions with both the LR and the PC in the
list."

However GCC generates both forms in function epilogues when compiling with
-mapcs. gas doesn't have a warning for these (I'm working on a patch to add
those to gas) which is probably why this hasn't been noticed yet.

We should fix GCC so that it doesn't generate deprecated sequences for ARMv7-A
and later.


             reply	other threads:[~2014-12-08 14:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 14:43 ktkachov at gcc dot gnu.org [this message]
2014-12-08 14:44 ` [Bug target/64224] " ktkachov at gcc dot gnu.org
2014-12-09  0:08 ` rearnsha at gcc dot gnu.org
2014-12-09  8:08 ` ktkachov at gcc dot gnu.org
2015-02-12 15:42 ` mshawcroft 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-64224-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).