public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeremi Piotrowski <jeremi.piotrowski@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: new computer : any advice ?
Date: Wed, 9 Sep 2015 21:35:07 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.20.1509092110170.20302@gentoo-tp.localdomain> (raw)
In-Reply-To: <55F07978.6040403@xunil.at>

On Wed, 9 Sep 2015, Stefan G. Weichinger wrote:

> On 09.09.2015 20:01, Stefan G. Weichinger wrote:
> > Digging up that thread now somewhere ...
>
> Ah, I even participated then ;-)
>
> AFAI understand gcc-5 should compile faster?
> And generate faster code in some cases?

No, and yes. Compilation is not affected in any way and runtime
performance can only be improved _if_ this stuff is explicitly used within
the code.

Meaning you would feel a difference in no less then 5 years when gcc-6 is
widely used and accelerator support is not restricted to intel MIC and
nvidia gpus. James is getting a bit ahead of himself calling this a
"game changer" - yeaaaaah... not really right now.

Right now this functionality is a toy for the HPC community and will stay
that way. To use it you have to build a separate offloading compiler, need
custom code used by few, and expensive hardware. The tree ebuild doesn't
even provide a way for enabling the accelerator support.


>
> ... does it use this new stuff anyway, do we need a specific USE-flag
> enabled (I can't spot it, looking for something like "acc" or "rdma"
> ;-)), do we need specific CFLAGS .. ?
>
> just curious.

I can't speak for RDMA (can't find any mention of it in gcc) because
that's an even more exotic thing than plain old accelerator support
(unless you run infiniband at home...), but the flags are:

    -fopenmp
    -foffload
    -fopenacc

However enabling them is as useful as having CFLAGS=-fopenmp currently. It
changes __nothing__ unless an application has openmp annotations, and the
ones that do should already provide a means of doing so in the build
system.

tldr: don't buy a dedicated gpu just because you read something on a
mailing list ;)



  reply	other threads:[~2015-09-09 19:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07 19:56 [gentoo-user] new computer : any advice ? Philip Webb
2015-09-07 20:55 ` Dale
2015-09-08 15:32 ` [gentoo-user] " James
2015-09-08 15:51   ` Stefan G. Weichinger
2015-09-08 16:00     ` Francisco Ares
2015-09-09  2:20     ` James
2015-09-09 18:01       ` Stefan G. Weichinger
2015-09-09 18:24         ` Stefan G. Weichinger
2015-09-09 19:35           ` Jeremi Piotrowski [this message]
2015-09-09 20:32             ` Stefan G. Weichinger
2015-09-09 21:52             ` james
2015-09-10  6:35               ` Fernando Rodriguez
2015-09-10 12:20                 ` james
2015-09-10 13:26                   ` Rich Freeman
2015-09-10 18:22                   ` Gevisz
2015-09-10 21:12                     ` james
2015-09-11  4:42                       ` Gevisz
2015-09-12  7:49                   ` [gentoo-user] Re: OT: GCC 5 Offloading Fernando Rodriguez
2015-09-10  2:22             ` [gentoo-user] Re: new computer : any advice ? james
2015-09-09 19:22         ` Mick
2015-09-09 19:35         ` Alan McKinnon

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=alpine.LNX.2.20.1509092110170.20302@gentoo-tp.localdomain \
    --to=jeremi.piotrowski@gmail.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