public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/103298] [12 regressions] regressions on arm after r12-5301
Date: Thu, 18 Nov 2021 11:36:41 +0000	[thread overview]
Message-ID: <bug-103298-4-YfgrWtnctk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103298-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
The test looks fragile.

The instructions TBB and TBH can only support forward branches.  If a label in
the list of switch targets is backwards then they can't be used and a
non-compressed table must be used.

My guess is that what's happening here is that with other changes to the code
generation all the branches are now forwards and that the TBB/TBH optimisation
can be legitimately applied.

  parent reply	other threads:[~2021-11-18 11:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  8:45 [Bug tree-optimization/103298] New: " clyon at gcc dot gnu.org
2021-11-17  8:49 ` [Bug tree-optimization/103298] " pinskia at gcc dot gnu.org
2021-11-17 21:38 ` pinskia at gcc dot gnu.org
2021-11-18  7:44 ` rguenth at gcc dot gnu.org
2021-11-18  9:38 ` [Bug testsuite/103298] " rguenth at gcc dot gnu.org
2021-11-18 11:36 ` rearnsha at gcc dot gnu.org [this message]
2022-05-06  8:31 ` jakub at gcc dot gnu.org
2023-05-08 12:23 ` rguenth at gcc dot gnu.org
2024-06-20  8:59 ` rguenth 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-103298-4-YfgrWtnctk@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).