public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New project: LLVM
Date: Fri, 19 Aug 2016 19:38:03 +0200	[thread overview]
Message-ID: <3fd1f3db-1ccd-50ff-5257-4fd3db6cdfda@gentoo.org> (raw)
In-Reply-To: <CAOnawYpyS2xhYgKGbWGxAO3MPfN=0pzAeg=tiGxXXXKJpwpQXw@mail.gmail.com>

On 19/08/16 17:15, C Bergström wrote:
> On Fri, Aug 19, 2016 at 11:01 PM, Luca Barbato <lu_zero@gentoo.org> wrote:
>> BTW is pathscale ready to be used as system compiler as well?
> 
> I wish, but no. We have known issues when building grub2, glibc and
> the Linux kernel at the very least. Someone* did report a long time
> ago that with their unofficial port, were able to build/boot the
> NetBSD kernel.
> (*A community dev we trusted with our sources and was helping us with
> portability across platforms)
> 
> The stuff with grub2 may potentially be fixed in the "near" future...
> the others are more tricky. In general if clang can do it, we have a
> strong chance as well.

I see, it is getting quite close =)

> As a philosophy - "we" aren't really trying to be the best generic
> compiler in the world. We aim more on optimizing as much for known
> targets. So if by system you mean, a compiler that would produce an
> "OS" which only runs on a single class of hardware, then yeah it could
> work at some point in the future. Specifically, on x86 we default on
> host CPU optimizations. So on newer Intel hardware it's easy to get a
> binary that won't run on AMD or older 64bit Intel.
> 
> More recently on ARMv8 - we turn on processor specific tuning. So
> while it may "run", the difference between APM's mustang and Cavium
> ThunderX is pretty big and running binaries intended for A and ran on
> B would certainly take a hit.. (this is just the tip of the iceberg)

This is not a problem for Gentoo, actually sounds a good match for one
of our many use-cases =)

> For HPC codes or anything where you get loops or computationally
> complex - the gloves are off and I could see big differences... (again
> being general and maybe a bit dramatic for fun)

I started to do some decoding benchmark across compiler version some
time ago, I should try to put in the mix your compiler as well and
eventually blog about it =)

lu


  reply	other threads:[~2016-08-19 17:38 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 [this message]
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
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=3fd1f3db-1ccd-50ff-5257-4fd3db6cdfda@gentoo.org \
    --to=lu_zero@gentoo.org \
    --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