public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: james <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] OT: GCC 5 Offloading
Date: Tue, 15 Sep 2015 03:11:37 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150915T045926-417@post.gmane.org> (raw)

Fernando Rodriguez <frodriguez.developer <at> outlook.com> writes:

> Do you know of any plans to enable offloading on the gentoo toolchain?

NO, but I'm sure some devs are keenly aware of this feature in gcc-5.


> I was able to build the offloading compiler using crossdev with a few hacks 
> and wrote an ebuild for Intel's simulator[2]. I will work on enabling the  
> host compiler tomorrow and may open a feature request and post patches 
> once I get it working. The changes needed to enable it on the host are 
> pretty trivial.

Sorry Fernando, I just now saw this thread on an old thread. I think that
'sys-cluster/ceph' is where I'd like to test your spin on the gcc-5.
Ceph has RDMA (RoCE) in the 0.94 branch (in portage). You are definately
ahead of me on practical gcc-5 experiments with offloading and other
new features.

You did not list your second reference. Where I can I get/git your
compiler and some brief suggestions on taking it for a test drive.

I'm not much interested in the Intel simulator, atm. I like to test on
old gear running gentoo:: borking is no big deal, if it happens.
Other codes keen to test gcc-5 (offloading) on are Apache-mesos and
Apache-spark and mesos-distcc.

Also, per this doc [1] you can get your own gentoo overlay to put
things up for wider experimentation, if you like.

[1] https://wiki.gentoo.org/wiki/Project:Overlays/Dev_Guide


Very cool, what you have done,
James




             reply	other threads:[~2015-09-15  3:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15  3:11 james [this message]
2015-09-15  7:22 ` [gentoo-user] OT: GCC 5 Offloading Fernando Rodriguez
2015-09-15 15:44   ` [gentoo-user] " james

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=loom.20150915T045926-417@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@lists.gentoo.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