public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/30442] Expanded array initialization can use memset builtin function Date: Wed, 12 Mar 2008 11:06:00 -0000 [thread overview] Message-ID: <20080312110519.24181.qmail@sourceware.org> (raw) In-Reply-To: <bug-30442-1649@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from ubizjak at gmail dot com 2008-03-12 11:05 ------- This still happens on mainline. I wonder if vectorizer infrastructure can be re-used here to detect unrolled and looped version of memset. In addition to loop that can be "vectorized", we have something resembling "vectorization" of straight code. And looking at comment #3, the rewards from real-world code look really promising. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30442
next prev parent reply other threads:[~2008-03-12 11:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-11 19:53 [Bug c/30442] New: Array " ubizjak at gmail dot com 2007-01-11 22:16 ` [Bug middle-end/30442] " pinskia at gcc dot gnu dot org 2007-01-14 5:01 ` [Bug middle-end/30442] Expanded array " pinskia at gcc dot gnu dot org 2007-11-09 13:09 ` johan dot walles at gmail dot com 2008-03-12 11:06 ` ubizjak at gmail dot com [this message] 2008-03-13 6:51 ` irar at il dot ibm dot com [not found] <bug-30442-4@http.gcc.gnu.org/bugzilla/> 2012-02-06 21:41 ` ubizjak at gmail dot com 2012-06-05 10:50 ` rguenth at gcc dot gnu.org 2012-06-05 12:38 ` rguenth at gcc dot gnu.org 2012-06-05 12:39 ` rguenth 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=20080312110519.24181.qmail@sourceware.org \ --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).