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/98931] [11 Regression] arm: Assembly fails with "branch out of range or not a multiple of 2" since r11-2012
Date: Thu, 11 Feb 2021 15:21:52 +0000	[thread overview]
Message-ID: <bug-98931-4-esumJixme3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98931-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrea Corallo <akrl@gcc.gnu.org>:

https://gcc.gnu.org/g:38c5703449c0638618ba6896f0d039c3868ad4e0

commit r11-7190-g38c5703449c0638618ba6896f0d039c3868ad4e0
Author: Andrea Corallo <andrea.corallo@arm.com>
Date:   Wed Feb 3 15:21:54 2021 +0100

    arm: Low overhead loop handle long range branches [PR98931]

    gcc/
            PR target/98931
            * config/arm/thumb2.md (*doloop_end_internal): Generate
            alternative sequence to handle long range branches.

    gcc/testsuite/
            PR target/98931
            * gcc.target/arm/pr98931.c: New testcase.

  parent reply	other threads:[~2021-02-11 15:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 12:40 [Bug target/98931] New: arm: Assembly fails with "branch out of range or not a multiple of 2" acoplan at gcc dot gnu.org
2021-02-02 12:52 ` [Bug target/98931] [11 Regression] " ktkachov at gcc dot gnu.org
2021-02-02 16:15 ` [Bug target/98931] [11 Regression] arm: Assembly fails with "branch out of range or not a multiple of 2" since r11-2012 jakub at gcc dot gnu.org
2021-02-02 16:26 ` jakub at gcc dot gnu.org
2021-02-02 16:30   ` Andrea Corallo
2021-02-02 16:31 ` andrea.corallo at arm dot com
2021-02-02 16:42 ` jakub at gcc dot gnu.org
2021-02-03 15:22   ` Andrea Corallo
2021-02-03 15:22 ` andrea.corallo at arm dot com
2021-02-03 15:30 ` jakub at gcc dot gnu.org
2021-02-03 15:38 ` jakub at gcc dot gnu.org
2021-02-03 16:38   ` Andrea Corallo
2021-02-05 15:13     ` Andrea Corallo
2021-02-03 16:38 ` andrea.corallo at arm dot com
2021-02-05 15:13 ` andrea.corallo at arm dot com
2021-02-05 15:53 ` jakub at gcc dot gnu.org
2021-02-05 16:03 ` akrl at gcc dot gnu.org
2021-02-09 13:41 ` akrl at gcc dot gnu.org
2021-02-11 15:21 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-11 15:29 ` akrl at gcc dot gnu.org
2021-02-12 14:19 ` 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-98931-4-esumJixme3@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).