public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uros at kss-loka dot si" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/18777] New: Redundant loop count insns in simple vectorized loop Date: Thu, 02 Dec 2004 08:47:00 -0000 [thread overview] Message-ID: <20041202084706.18777.uros@kss-loka.si> (raw) The modifies testcase from PR18767 shows the problem where loop count variables still remains in vectorized loop. Compiling the modified testcase with 'g++ -O2 -march=pentium4 -ftree-vectorize' following code is produced for the first loop: ... leal -24(%ebp), %esi leal -40(%ebp), %ebx leal -56(%ebp), %ecx xorl %eax, %eax xorl %edx, %edx .L2: addl $1, %eax movaps (%edx,%esi), %xmm0 mulps (%ebx,%edx), %xmm0 movaps %xmm0, (%edx,%ecx) addl $16, %edx cmpl $1, %eax jne .L2 ... It looks that the compiler does not figure out that the conditional jump is never taken. However with 'g++ -O2 -march=pentium4 -ftree-vectorize -funroll-loops' generated code is a lot better: ... movaps -24(%ebp), %xmm0 mulps -40(%ebp), %xmm0 movaps %xmm0, -56(%ebp) ... Uros. -- Summary: Redundant loop count insns in simple vectorized loop Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uros at kss-loka dot si CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18777
next reply other threads:[~2004-12-02 8:47 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-02 8:47 uros at kss-loka dot si [this message] 2004-12-02 13:22 ` [Bug tree-optimization/18777] " pinskia at gcc dot gnu dot org 2004-12-02 13:31 ` pinskia at gcc dot gnu dot org 2005-06-12 3:19 ` pinskia at gcc dot gnu dot 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=20041202084706.18777.uros@kss-loka.si \ --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).