From: Andi Kleen <andi@firstfloor.org>
To: Bernd Schmidt <bschmidt@redhat.com>
Cc: Gary Funck <gary@intrepid.com>,
Gcc Patches <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>,
Richard Henderson <rth@redhat.com>,
Meador Inge <meadori@codesourcery.com>,
Jakub Jelinek <jakub@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
Nenad Vukicevic <nenad@intrepid.com>
Subject: Re: RFC: Merge the GUPC branch into the GCC 6.0 trunk
Date: Tue, 01 Dec 2015 15:11:00 -0000 [thread overview]
Message-ID: <87bnaauru6.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <565D8254.5070205@redhat.com> (Bernd Schmidt's message of "Tue, 1 Dec 2015 12:19:48 +0100")
Bernd Schmidt <bschmidt@redhat.com> writes:
> I'm worried we'll end up carrying
> something around as a burden that is of no practical use (considering
> we already support the more widespread OpenMP).
I'm not an expert on UPC, but from glancing over the description it
seems to target a distributed message passing programing model,
which is very different from OpenMP. I don't think any of the existing
parallelization models in gcc (OpenMP, cilk) support that niche.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2015-12-01 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 5:31 Gary Funck
2015-12-01 11:12 ` Richard Biener
2015-12-01 13:58 ` Jeff Law
2015-12-01 16:34 ` Gary Funck
2015-12-02 9:40 ` Richard Biener
2015-12-05 22:57 ` Gary Funck
2015-12-06 7:58 ` Richard Biener
2015-12-01 11:19 ` Bernd Schmidt
2015-12-01 15:11 ` Andi Kleen [this message]
2015-12-01 15:23 ` Richard Biener
2015-12-02 17:08 ` Gary Funck
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=87bnaauru6.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=bschmidt@redhat.com \
--cc=gary@intrepid.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=meadori@codesourcery.com \
--cc=nenad@intrepid.com \
--cc=rguenther@suse.de \
--cc=rth@redhat.com \
/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).