public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "C Bergström" <cbergstrom@pathscale.com>
To: "Anthony G. Basile" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] New project: LLVM
Date: Sat, 20 Aug 2016 05:05:01 +0800	[thread overview]
Message-ID: <CAOnawYr98ExSK-DgqT+2+-myxJr8gzKhfoaqx+_ArSrB7q+wzw@mail.gmail.com> (raw)
In-Reply-To: <905c6752-af7d-f19e-2698-b31f2ee5f89d@verizon.net>

On Sat, Aug 20, 2016 at 4:52 AM, james <garftd@verizon.net> wrote:

<snip>

>> Back to my own glass house.. It will take a few years, but I am trying
>> to make it easier (internally) to expose in some clear way all the
>> pieces which compose a fine tuning per-processor. If this was "just"
>> scheduling models it would be really easy, but it's not.. Those
>> latencies and other magic bits decide things like.. "should I unroll
>> this loop or do something else" and then you venture into the land of
>> accelerators where a custom regalloc may be what you really need and
>> *nothing* off the shelf fits to meet your goals.. (projects like that
>> can take 9 months and in the end only give a general 1-5% median
>> performance gain..)
>
>
> If this is your mantra, I resend the generous comments. Cray use to work
> that way, milking the Petroleum Industry for tons of money, but, things have
> changed and the change is accelerating, rapidly. Perhaps too much off those
> Cray patents that your company owns are leaking toxins into the brain-trust
> where you park?
>
> Vendor walk-back is sad, imho. ymmv.
>
> Best of luck to your company's  5-year plan....

I have no idea what on earth you were trying to say in most of your
reply. I am speaking only from a compiler perspective. Nothing more
and nothing less.. it may be my difficultly to describe the target
level and processor specific optimization choices a compiler *must*
make.

Beyond not understanding your email, I found it insulting. So please
keep rude comments to yourself.

So again to try to explain the technical side of this - We can't and
have no desire to optimize for every class of processor on the planet.
We have a narrow band of focus on mostly HPC centric code patterns and
processors which are are typically used in HPC workloads. I'd love to
expand past this, but we're a small company and that's our niche.
There's no walking back or trying to claim to be something we're not..
this is pure honest transparency. (imagine it like - do one thing and
do it well)

The only special note I'd add on to this - the CPU isn't where we
spend most of our time tuning, it's by far more on the accelerator
support.


  reply	other threads:[~2016-08-19 21:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 16:22 [gentoo-dev] New project: LLVM Michał Górny
2016-08-18 13:48 ` Ian Bloss
2016-08-18 13:56   ` C Bergström
2016-08-18 23:33     ` Lei Zhang
2016-08-19  2:07       ` cbergstrom
2016-08-19  2:40         ` Lei Zhang
2016-08-19  3:11           ` C Bergström
2016-08-19 15:01             ` Luca Barbato
2016-08-19 15:15               ` C Bergström
2016-08-19 17:38                 ` Luca Barbato
2016-08-19 18:02                 ` james
2016-08-19 18:20                   ` C Bergström
2016-08-19 20:52                     ` james
2016-08-19 21:05                       ` C Bergström [this message]
2016-08-19 21:41                         ` james
2016-08-20  5:45                           ` C Bergström
2016-08-19 16:54             ` Lei Zhang
2016-08-19 17:13               ` C Bergström
2016-08-19 17:34                 ` Luca Barbato
2016-08-21  1:10                 ` Lei Zhang

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=CAOnawYr98ExSK-DgqT+2+-myxJr8gzKhfoaqx+_ArSrB7q+wzw@mail.gmail.com \
    --to=cbergstrom@pathscale.com \
    --cc=gentoo-dev@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