public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/53081] memcpy/memset loop recognition
Date: Mon, 23 Apr 2012 06:53:00 -0000 [thread overview]
Message-ID: <bug-53081-4-kQH7iKwFEm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53081-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53081
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #5 from Alexander Monakov <amonakov at gcc dot gnu.org> 2012-04-23 06:53:11 UTC ---
The memset part can be handled by -ftree-loop-distribution (not enabled at -O3)
next prev parent reply other threads:[~2012-04-23 6:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 4:52 [Bug middle-end/53081] New: " xinliangli at gmail dot com
2012-04-23 5:03 ` [Bug middle-end/53081] " pinskia at gcc dot gnu.org
2012-04-23 5:07 ` pinskia at gcc dot gnu.org
2012-04-23 5:34 ` xinliangli at gmail dot com
2012-04-23 5:35 ` xinliangli at gmail dot com
2012-04-23 6:53 ` amonakov at gcc dot gnu.org [this message]
2012-04-23 6:55 ` pinskia at gcc dot gnu.org
2012-04-23 8:19 ` jakub at gcc dot gnu.org
2012-04-23 10:27 ` [Bug tree-optimization/53081] " rguenth at gcc dot gnu.org
2012-06-05 9:25 ` rguenth at gcc dot gnu.org
2012-06-06 9:45 ` rguenth at gcc dot gnu.org
2012-06-06 9:46 ` rguenth at gcc dot gnu.org
2012-06-06 9:46 ` rguenth at gcc dot gnu.org
2012-06-06 11:32 ` Joost.VandeVondele at mat dot ethz.ch
2012-06-06 11:39 ` rguenther at suse dot de
2012-06-06 11:54 ` Joost.VandeVondele at mat dot ethz.ch
2012-06-06 12:43 ` izamyatin at gmail dot com
2012-06-20 8:45 ` izamyatin 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-53081-4-kQH7iKwFEm@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).