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/66890] function splitting only works with profile feedback Date: Tue, 16 May 2023 22:26:36 +0000 [thread overview] Message-ID: <bug-66890-4-b35JRUfpRD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66890-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66890 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Really for this loop, I would have assume to be split into 3 different loops like: volatile int count; int main() { int i; for (i = 0; i < 999; i++) { if (i == 999) count *= 2; count++; } for (; i < 999+1; i++) { if (i == 999) count *= 2; count++; } for (; i < 100000; i++) { if (i == 999) count *= 2; count++; } } And then it would not have an extra branch inside the loop itself either.
prev parent reply other threads:[~2023-05-16 22:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-15 22:17 [Bug rtl-optimization/66890] New: " andi-gcc at firstfloor dot org 2015-07-16 7:05 ` [Bug rtl-optimization/66890] " andi-gcc at firstfloor dot org 2015-07-17 17:42 ` andi-gcc at firstfloor dot org 2023-05-16 22:26 ` pinskia at gcc dot gnu.org [this message]
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-66890-4-b35JRUfpRD@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).