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 middle-end/39275] -funroll-loop fails Date: Sat, 21 Jan 2012 08:11:00 -0000 [thread overview] Message-ID: <bug-39275-4-sLeiOo8qEz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-39275-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39275 --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-01-21 07:20:42 UTC --- Here is a reduced testcase: struct vector { char *_M_start; char *_M_finish; }; struct LoopBase { static LoopBase *f(); LoopBase *ParentLoop; vector SubLoops; ~LoopBase() { for (int i = 0, e = SubLoops._M_finish - SubLoops._M_start; i != e; ++i) delete f(); } }; void deleteLoopFromQueue(LoopBase *L, int b) { if (L->ParentLoop) while (L->SubLoops._M_start != L->SubLoops._M_finish)return; else while (L->SubLoops._M_start != L->SubLoops._M_finish)return; delete L; } --- CUT --- The delete loop is actually an empty loop but the tree level does not see that for some reason: # prephitmp.36_112 = PHI <prephitmp.36_6(4), prephitmp.36_3(3)> # prephitmp.36_21 = PHI <prephitmp.36_6(4), prephitmp.36_3(3)> D.2385_15 = (long int) prephitmp.36_21; D.2387_17 = (long int) prephitmp.36_112; Those PHIs are the same.
next prev parent reply other threads:[~2012-01-21 7:22 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-39275-4@http.gcc.gnu.org/bugzilla/> 2012-01-19 7:33 ` pinskia at gcc dot gnu.org 2012-01-21 8:11 ` pinskia at gcc dot gnu.org [this message] 2021-12-23 5:54 ` pinskia at gcc dot gnu.org 2009-02-23 16:10 [Bug middle-end/39275] New: " linuxl4 at sohu dot com 2009-02-23 16:15 ` [Bug middle-end/39275] " linuxl4 at sohu dot com 2009-04-19 17:30 ` linuxl4 at sohu 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-39275-4-sLeiOo8qEz@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).