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>
Cc: llvm@gentoo.org
Subject: Re: [gentoo-dev] New project: LLVM
Date: Sat, 20 Aug 2016 01:13:54 +0800	[thread overview]
Message-ID: <CAOnawYroEQdgL-jDfp34+N=gMhtBbH02rV=5aa0WQpv22kaXAQ@mail.gmail.com> (raw)
In-Reply-To: <CAOYuCc3ot4xHe0r1k8WPxX+Pnt8dQ2-yuBrLex3-OQabtXNtSQ@mail.gmail.com>

I finally got it to build and here's the size numbers
952K    ./lib/libc++abi.a
616K    ./lib/libc++abi.so.1.0

If the above isn't enough motivation and you really want benchmarks
which prove it's a pig... I'll try to figure something else

Not exactly a 1:1 comparison because I think other things are mixed in, but...
352K    /usr/lib/gcc/x86_64-linux-gnu/4.9/libsupc++.a
356K    /usr/lib/gcc/x86_64-linux-gnu/5/libsupc++.a

In the land of HPC we frequently statically link stuff... not that
864KB is big by any sort of modern definition, but it does raise
questions..


On Sat, Aug 20, 2016 at 12:54 AM, Lei Zhang <zhanglei.april@gmail.com> wrote:
> 2016-08-19 11:11 GMT+08:00 C Bergström <cbergstrom@pathscale.com>:
>> I think you're getting a bit confused
>>
>> libsupc++ is the default now, from GNU
>>
>> libcxxabi is the bloated runtime from Apple
>>
>> libcxxrt is the faster c++ runtime, PathScale+David Chisnall, which
>> PathScale and FreeBSD use by default. We don't need a version number
>> because it's pretty much rock solid stable for a while.
>> I'd encourage you to consider libcxxrt for at least the code size and
>> performance reasons. Build it and you'll see. Locally my unoptimized
>> libcxxrt.so is like 88K. How much is your libcxxabi (static and
>> shared)
>>
>> 88K    /opt/enzo-2016-06-26/lib/6.0.983/x8664/64/libcxxrt.so
>> 140K    /opt/enzo-2016-06-26/lib/6.0.983/x8664/64/libcxxrt.a
>> // This seems larger than I remember and I need to check why.
>>
>> https://github.com/pathscale/libcxxrt
>
> Currently libcxxrt is the default ABI lib for libc++ in Gentoo. I mean
> to replace it with libc++abi in that context.
>
> I'm interested in benchmarking to reveal the claimed difference in
> performance. Perhaps I can build the same program against libcxxrt and
> libc++abi respectively and see how it behaves. Do you have some hints
> on what kind of programs I should test?
>
>
> Thanks,
> Lei
>


  reply	other threads:[~2016-08-19 17:14 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
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 [this message]
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='CAOnawYroEQdgL-jDfp34+N=gMhtBbH02rV=5aa0WQpv22kaXAQ@mail.gmail.com' \
    --to=cbergstrom@pathscale.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=llvm@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