public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96770] -mpure-code produces suboptimal code for relocations with small offset for thumb-1
Date: Mon, 02 Nov 2020 07:35:31 +0000	[thread overview]
Message-ID: <bug-96770-4-vOF8COHPYi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96770-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Christophe Lyon <clyon@gcc.gnu.org>:

https://gcc.gnu.org/g:c3c3e2c9e88e25a410a2fe089782b094e911bb39

commit r11-4599-gc3c3e2c9e88e25a410a2fe089782b094e911bb39
Author: Christophe Lyon <christophe.lyon@linaro.org>
Date:   Mon Nov 2 07:34:50 2020 +0000

    arm: Improve handling of relocations with small offsets with -mpure-code on
v6m (PR96770)

    With -mpure-code on v6m (thumb-1), we can use small offsets with
    upper/lower relocations to avoid the extra addition of the
    offset.

    This patch accepts expressions symbol+offset as legitimate constants
    when the literal pool is disabled, making sure that the offset is
    within the range supported by thumb-1 [0..255] as described in the
    AAELF32 documentation.

    It also makes sure that thumb1_movsi_insn emits an error in case we
    try to use it with an unsupported RTL construct.

    2020-09-28  Christophe Lyon  <christophe.lyon@linaro.org>

            gcc/
            PR target/96770
            * config/arm/arm.c (thumb_legitimate_constant_p): Accept
            (symbol_ref + addend) when literal pool is disabled.
            (arm_valid_symbolic_address_p): Add support for thumb-1 without
            MOVT/MOVW.
            * config/arm/thumb1.md (*thumb1_movsi_insn): Accept (symbol_ref +
            addend) in the pure-code alternative.

            gcc/testsuite/
            PR target/96770
            * gcc.target/arm/pure-code/pr96770.c: New test.

  parent reply	other threads:[~2020-11-02  7:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 13:30 [Bug target/96770] New: " clyon at gcc dot gnu.org
2020-09-08 12:51 ` [Bug target/96770] " clyon at gcc dot gnu.org
2020-09-28  9:10 ` clyon at gcc dot gnu.org
2020-11-02  7:35 ` cvs-commit at gcc dot gnu.org [this message]
2020-11-09 12:26 ` clyon at gcc dot gnu.org
2021-03-28 19:01 ` cvs-commit at gcc dot gnu.org
2021-04-16 19:59 ` cvs-commit 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-96770-4-vOF8COHPYi@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).