public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/36281] vector code is not parallelized
Date: Mon, 19 Jul 2010 08:25:00 -0000 [thread overview]
Message-ID: <20100719082502.13607.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36281-7780@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from rob1weld at aol dot com 2010-07-19 08:25 -------
> ... this does not get parallelized at all ...
Also see 34501
Perhaps we could make some use of Pluto. It is a fully automatic (C to OpenMP
C) parallelizer that makes code amenable to auto-vectorization.
http://pluto-compiler.sourceforge.net/
Also see these Parallelizers:
http://cri.ensmp.fr/pips/ or http://pips4u.org/
There was something I found a few days ago from here that I can no longer
locate
http://en.wikipedia.org/wiki/Automatic_parallelization
It would be great to take that inner loop (if it were much larger) and
'Kernelize' it for co-processing on our Graphics Card. We could expand GCCs
'x-parallelize-x' and threading options to automatically find the sweeter spots
to offload for co=processing (on a GPU, using OpenCL).
Barra - NVIDIA G80 GPU Functional Simulator
http://gpgpu.univ-perp.fr/index.php/Barra
If we were 'allowed' to call a post-processor (like LTO used to do) we could
call ATI's GPU SDK which supports OpenCL and outputs code BOTH to x86 and it's
own GPUs.
Commercial Projects:
Auto-parallelizer and SIMDinator by Dalsoft
http://www.dalsoft.com/documentation_simdinator.html
NVidia's PTX
http://en.wikipedia.org/wiki/Parallel_Thread_Execution
Cray's work with LLVM
http://llvm.org/devmtg/2009-10/Greene_180k_Cores.pdf
Larrabee
http://www.drdobbs.com/architecture-and-design/216402188?pgno=5
Rob
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36281
prev parent reply other threads:[~2010-07-19 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 19:26 [Bug tree-optimization/36281] New: vectorized code " spop at gcc dot gnu dot org
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 [this message]
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=20100719082502.13607.qmail@sourceware.org \
--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).