public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/108826] Inefficient address generation on POWER and RISC-V
Date: Thu, 16 Feb 2023 17:56:47 +0000	[thread overview]
Message-ID: <bug-108826-4-jiGEArUQCA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108826-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
AARCH64 looks ok too because of the use of more complex adddresses:
        ldr     w0, [x0, #:lo12:.LANCHOR0]
        and     w0, w2, w0, lsr 6
        add     x0, x0, 200
        ldr     w0, [x1, x0, lsl 2]

  reply	other threads:[~2023-02-16 17:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 17:53 [Bug rtl-optimization/108826] New: " tkoenig at gcc dot gnu.org
2023-02-16 17:56 ` pinskia at gcc dot gnu.org [this message]
2023-02-16 18:00 ` [Bug rtl-optimization/108826] " pinskia at gcc dot gnu.org
2023-02-16 18:00 ` pinskia at gcc dot gnu.org
2023-02-16 18:09 ` pinskia at gcc dot gnu.org
2023-02-16 18:21 ` palmer at gcc dot gnu.org
2023-02-16 18:25 ` pinskia at gcc dot gnu.org
2023-09-28 19:55 ` pinskia 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-108826-4-jiGEArUQCA@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).