public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/50693] Loop optimization restricted by GOTOs
Date: Tue, 11 Oct 2011 14:46:00 -0000 [thread overview]
Message-ID: <bug-50693-4-RacgXJrYzD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50693-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50693
--- Comment #19 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-10-11 14:45:22 UTC ---
(In reply to comment #17)
> LLVM appears to be able to recognize memset of any value, not just zero. And
> apparently performs control flow simplification before attempting to recognize
> the idiom, so it can expose the loop created by the convoluted GOTOs.
I suppose you can no longer debug that though (break at the labels by
name), even when disabling the memset pattern detection?
next prev parent reply other threads:[~2011-10-11 14:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 22:45 [Bug c/50693] New: Slightly different loop body leads to 5.5x slower performance alex.gaynor at gmail dot com
2011-10-10 22:52 ` [Bug c/50693] " alex.gaynor at gmail dot com
2011-10-10 22:54 ` [Bug tree-optimization/50693] Slightly different loop body leads not vectoring loop pinskia at gcc dot gnu.org
2011-10-10 22:55 ` pinskia at gcc dot gnu.org
2011-10-10 23:57 ` dje at gcc dot gnu.org
2011-10-11 0:04 ` dje at gcc dot gnu.org
2011-10-11 0:22 ` dje at gcc dot gnu.org
2011-10-11 0:23 ` pinskia at gcc dot gnu.org
2011-10-11 1:12 ` [Bug tree-optimization/50693] Loop optimization restricted by GOTOs dje at gcc dot gnu.org
2011-10-11 1:24 ` pinskia at gcc dot gnu.org
2011-10-11 1:35 ` dje at gcc dot gnu.org
2011-10-11 7:15 ` irar at il dot ibm.com
2011-10-11 14:07 ` dje at gcc dot gnu.org
2011-10-11 14:13 ` rguenth at gcc dot gnu.org
2011-10-11 14:15 ` paolo.carlini at oracle dot com
2011-10-11 14:35 ` rguenth at gcc dot gnu.org
2011-10-11 14:36 ` rguenth at gcc dot gnu.org
2011-10-11 14:40 ` dje at gcc dot gnu.org
2011-10-11 14:44 ` rguenth at gcc dot gnu.org
2011-10-11 14:46 ` rguenth at gcc dot gnu.org [this message]
2011-10-11 14:51 ` jakub at gcc dot gnu.org
2011-10-11 16:04 ` alex.gaynor at gmail dot com
2011-10-12 15:21 ` rguenth at gcc dot gnu.org
2011-10-25 4:48 ` aoliva at gcc dot gnu.org
2011-11-04 17:18 ` jakub at gcc dot gnu.org
2011-11-05 19:59 ` jakub at gcc dot gnu.org
2011-11-05 20:09 ` alex.gaynor at gmail dot com
2012-03-26 10:35 ` jakub 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-50693-4-RacgXJrYzD@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: link
Be 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).