public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d.g.gorbachev at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/48128] New: Excessive code generated for vectorized loop Date: Tue, 15 Mar 2011 00:02:00 -0000 [thread overview] Message-ID: <bug-48128-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48128 Summary: Excessive code generated for vectorized loop Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: d.g.gorbachev@gmail.com Target: i686-*-* Created attachment 23658 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23658 Testcase (compile with `-O3 -march=pentium3')
next reply other threads:[~2011-03-15 0:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-15 0:02 d.g.gorbachev at gmail dot com [this message] 2011-03-15 0:57 ` [Bug rtl-optimization/48128] " pinskia at gcc dot gnu.org 2011-03-15 2:00 ` d.g.gorbachev at gmail dot com 2011-03-15 10:32 ` rguenth at gcc dot gnu.org 2014-06-19 5:35 ` d.g.gorbachev at gmail dot com 2021-08-27 5:24 ` pinskia 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-48128-4@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).