public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vineetg 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: Fri, 04 Aug 2023 22:30:48 +0000 [thread overview] Message-ID: <bug-106265-4-7ff3HNK2Oa@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 Vineet Gupta <vineetg at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vineetg at gcc dot gnu.org --- Comment #11 from Vineet Gupta <vineetg at gcc dot gnu.org> --- Revisited this with gcc-13. The reduced test case no longer shows the extraneous LI 4096 (although the full test still does). The key here is -funroll-loops which is needed for original issue to show as well. The was with middle-end update: commit 19295e8607da2f743368fe6f5708146616aafa91 Author: Richard Biener <rguenther@suse.de> Date: Mon Oct 24 09:51:32 2022 +0200 tree-optimization/100756 - niter analysis and folding niter analysis, specifically the part trying to simplify the computed maybe_zero condition against the loop header copying condition, is confused by us now simplifying _15 = n_8(D) * 4; if (_15 > 0) to _15 = n_8(D) * 4; if (n_8(D) > 0) which is perfectly sound at the point we do this transform. One solution might be to involve ranger in this simplification, another is to be more aggressive when expanding expressions - the condition we try to simplify is _15 > 0, so all we need is expanding that to n_8(D) * 4 > 0.
next prev parent reply other threads:[~2023-08-04 22:30 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 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 [this message] 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-7ff3HNK2Oa@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).