public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ak at muc dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/16362] New: i386/x86-64 backend missing logical vector operations
Date: Sun, 04 Jul 2004 19:34:00 -0000	[thread overview]
Message-ID: <20040704193415.16362.ak@muc.de> (raw)

The vectorization test suite currently has a few failures that happen
because i386 is missing patterns for logical vector operations.
Altivec got these recently.

> This means the i386 backend needs new patterns for logical operations
> like you added to altivec.md ?

I suspect so.

> FAIL: gcc.dg/tree-ssa-vect/tree-ssa-vect-17.c scan-tree-dump-times
vectorized 3 loops 1
> FAIL: gcc.dg/tree-ssa-vect/tree-ssa-vect-18.c scan-tree-dump-times
vectorized 3 loops 1
> FAIL: gcc.dg/tree-ssa-vect/tree-ssa-vect-19.c scan-tree-dump-times
vectorized 3 loops 1
> FAIL: gcc.dg/tree-ssa-vect/tree-ssa-vect-20.c scan-tree-dump-times
vectorized 3 loops 1

bitwise operations - may need to add new patterns to i*86 (see
http://gcc.gnu.org/ml/gcc-patches/2004-04/msg00907.html).

-- 
           Summary: i386/x86-64 backend missing logical vector operations
           Product: gcc
           Version: lno
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ak at muc dot de
                CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: i?86-*-*, x86_64-*-*


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16362


             reply	other threads:[~2004-07-04 19:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-04 19:34 ak at muc dot de [this message]
2004-07-04 19:35 ` [Bug target/16362] " pinskia at gcc dot gnu dot org
2005-01-12  6:42 ` 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=20040704193415.16362.ak@muc.de \
    --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).