public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106265] RISC-V SPEC2017 507.cactu code bloat due to address generation Date: Tue, 12 Jul 2022 06:44:39 +0000 [thread overview] Message-ID: <bug-106265-4-ORFpAs7jKC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106265-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106265 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- So why do we even emit unsupported 'li 4096' and leave it to the linker to "optimize(?)"? At least the cost of this should be reflected - IIRC powerpc recently got improvements for similar cases by changing the targets rtx_cost hook to properly const SET from CONST_INT so that CSE doesn't leave so many sets from constants around. OTOH LRA rematerialization also could be the culprit, thinking rematerializing the constant is cheaper than spilling a register holding it.
next prev parent reply other threads:[~2022-07-12 6:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-11 23:13 [Bug target/106265] New: " vineet.gupta at linux dot dev 2022-07-11 23:23 ` [Bug target/106265] " vineet.gupta at linux dot dev 2022-07-11 23:25 ` vineet.gupta at linux dot dev 2022-07-11 23:27 ` vineet.gupta at linux dot dev 2022-07-11 23:37 ` vineet.gupta at linux dot dev 2022-07-12 6:44 ` rguenth at gcc dot gnu.org [this message] 2022-07-12 7:51 ` Andrew Waterman 2022-07-12 7:52 ` andrew at sifive dot com 2022-07-12 20:18 ` vineet.gupta at linux dot dev 2022-07-21 21:09 ` vineet.gupta at linux dot dev 2022-07-21 21:21 ` vineet.gupta at linux dot dev 2022-07-22 21:39 ` vineet.gupta at linux dot dev 2023-08-04 22:30 ` vineetg at gcc dot gnu.org 2024-05-28 22:40 ` vineetg 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-106265-4-ORFpAs7jKC@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).