public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ysrumyan at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/68021] [6 Regression] ice in rewrite_use_nonlinear_expr with -O3 Date: Wed, 21 Oct 2015 09:48:00 -0000 [thread overview] Message-ID: <bug-68021-4-LcIm5zdPcY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-68021-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68021 --- Comment #4 from Yuri Rumyantsev <ysrumyan at gmail dot com> --- Indeed, there is an issue with outer-loop unswitching - it should not be performed for infinite loops. But if we slightly modify test if finite outer-loop we will get the same error: char a; void fn1(char *p1, int p2, int p3) { int i, x; for (i = 0; i < 10; i++) { for (x = 0; x < p3; x++) { *p1 = a; p1--; } p1 += p2; } } I assume that sccp is responsible for it.
next prev parent reply other threads:[~2015-10-21 9:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-19 18:07 [Bug c++/68021] New: " dcb314 at hotmail dot com 2015-10-20 8:09 ` [Bug tree-optimization/68021] [6 Regression] " rguenth at gcc dot gnu.org 2015-10-20 9:09 ` mpolacek at gcc dot gnu.org 2015-10-20 16:05 ` ysrumyan at gmail dot com 2015-10-21 9:48 ` ysrumyan at gmail dot com [this message] 2015-10-21 12:46 ` ysrumyan at gmail dot com
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-68021-4-LcIm5zdPcY@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).