public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/28920]  New: vectorizer produces vector long long on powerpc-linux-gnu (and vector long on powerpc64)
Date: Fri, 01 Sep 2006 06:31:00 -0000	[thread overview]
Message-ID: <bug-28920-6528@http.gcc.gnu.org/bugzilla/> (raw)

Take the following testcase:
extern char lanip[3][40];
typedef struct
{
  char *t[4];
}tx_typ;
int set_names (void)
{
  static tx_typ tt1;
  int ln;
  for (ln = 0; ln < 4; ln++)
      tt1.t[ln] = lanip[1];
}

-----
With -O2 -ftree-vectorize -maltivec, we produce a vector long long and we get
worse code than just doing the scalar code as VMX does not have a vector long
long mode.  We really should be asking the target if we support a vector mode.
I noticed this while looking into PR 28915.


-- 
           Summary: vectorizer produces vector long long on powerpc-linux-
                    gnu (and vector long on powerpc64)
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org
GCC target triplet: piowerpc-linux-gnu


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


             reply	other threads:[~2006-09-01  6:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01  6:31 pinskia at gcc dot gnu dot org [this message]
2007-07-09  7:35 ` [Bug tree-optimization/28920] " 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=bug-28920-6528@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).