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/106583] New: Suboptimal immediate generation on aarch64 Date: Thu, 11 Aug 2022 09:01:33 +0000 [thread overview] Message-ID: <bug-106583-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106583 Bug ID: 106583 Summary: Suboptimal immediate generation on aarch64 Product: gcc Version: unknown Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: ktkachov at gcc dot gnu.org Target Milestone: --- Target: aarch64 A simple codegen issue: unsigned long long foo (void) { return 0x7efefefefefefeff; } generates at -O2 foo: mov x0, 65279 movk x0, 0xfefe, lsl 16 movk x0, 0xfefe, lsl 32 movk x0, 0x7efe, lsl 48 ret whereas LLVM can do: foo: // @foo mov x0, #-72340172838076674 movk x0, #65279 movk x0, #32510, lsl #48 ret Should be a matter of just making aarch64_internal_mov_immediate in aarch64.cc a bit smarter
next reply other threads:[~2022-08-11 9:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-11 9:01 ktkachov at gcc dot gnu.org [this message] 2022-10-19 16:14 ` [Bug target/106583] " pinskia at gcc dot gnu.org 2022-10-19 16:14 ` pinskia at gcc dot gnu.org 2022-10-24 14:36 ` cvs-commit at gcc dot gnu.org 2022-10-25 12:05 ` wilco at gcc dot gnu.org 2022-10-31 19:21 ` 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-106583-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: linkBe 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).