This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/50693] Loop optimization restricted by GOTOs
- From: "dje at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 11 Oct 2011 14:06:34 +0000
- Subject: [Bug tree-optimization/50693] Loop optimization restricted by GOTOs
- Auto-submitted: auto-generated
- References: <bug-50693-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50693
--- Comment #12 from David Edelsohn <dje at gcc dot gnu.org> 2011-10-11 14:06:34 UTC ---
Because the vectorizer analysis occurs fairly early, I guess there is not a lot
of opportunity to clean up the control flow.
Should GCC have a memset peephole pass like LLVM?