public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spop at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/36281]  New: vectorized code not parallelized
Date: Tue, 20 May 2008 19:26:00 -0000	[thread overview]
Message-ID: <bug-36281-7780@http.gcc.gnu.org/bugzilla/> (raw)

The testcase of PR36181 should be parallelized after being vectorized.

/* { dg-do compile } */
/* { dg-options "-O3 -ftree-parallelize-loops=2" } */

int foo ()
{
  int i, sum = 0, data[1024];

  for(i = 0; i<1024; i++)
    sum += data[i];

  return sum;
}

The fix for PR36181 was to disable the parallelization of a loop when
one of the phi nodes had a vector type.  This testcase should also be
parallelized.  See also the comments from the fix for PR36181:
http://gcc.gnu.org/ml/gcc-patches/2008-05/msg01217.html


-- 
           Summary: vectorized code not parallelized
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: spop at gcc dot gnu dot org
        ReportedBy: spop at gcc dot gnu dot org


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


             reply	other threads:[~2008-05-20 19:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 19:26 spop at gcc dot gnu dot org [this message]
2008-05-20 19:42 ` [Bug tree-optimization/36281] " pinskia at gcc dot gnu dot org
2008-12-28  3:26 ` [Bug tree-optimization/36281] vector code is " pinskia at gcc dot gnu dot org
2010-07-19  8:25 ` rob1weld at aol dot com

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-36281-7780@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).