Re: [gentoo-dev] New project: LLVM

[cbergstrom]

That seems a lot like what we've already done. I guess a GSOC student is 
working on the libcxxabi piece. The only advantage to using our runtime, 
libcxxrt, is performance and code size.‎ 

  Original Message  
From: Lei Zhang
Sent: Friday, August 19, 2016 06:34
To: gentoo-dev@lists.gentoo.org
Reply To: gentoo-dev@lists.gentoo.org
Cc: gentoo-dev-annou...@lists.gentoo.org
Subject: Re: [gentoo-dev] New project: LLVM

2016-08-18 21:56 GMT+08:00 C Bergström :
> @mgorny may be able to help with some of this and has quite a bit of
> experience building clang/llvm. Where I work we use a "wrapper" that
> helps coordinate a lot of the moving pieces.
>
> https://github.com/pathscale/llvm-suite/
>
> This may not be the perfect "gentoo" way to handle it, but the
> approach would produce a clean and correct compiler. With llvm
> dependencies getting more and more complicated, I'm not sure if it
> would be possible to have both a gnu-free and also perfect
> 1-project-source-repo:1-ebuild ratio.

Currently the ebuilds for libunwind, libc++abi and libc++ all involve
some hackery to support standalone build. And the package clang is
just a placeholder, while it's actually built in llvm.

Maybe we can put them all into the llvm package, and control what
components to build via USE flags.


Lei

Re: [gentoo-dev] On banning merge commits

[cbergstrom]

Don't be crazy - I know many developer groups which dislike merge commits. That 
nonlinear work flow is just a mess long term.

  Original Message  
From: Michał Górny
Sent: Sunday, May 8, 2016 13:09
To: Patrice Clement
Reply To: gentoo-dev@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] On banning merge commits

On Sun, 8 May 2016 01:52:22 +0200
Patrice Clement  wrote:

> Hi gents
> 
> After yet another discussion about git in the #gentoo-dev channel tonight, the
> topic of merge commits came up for the umpteenth time.
> 
> We all seem to agree merge commits are really bad design, add clutter to the
> log graph after a while and should be banned altogether from reaching the
> central repository.
> 
> As of now, no policy is in place yet to keep developers from pushing merge
> commits.
> 
> What is the correct course of action? I would very much like it to be worded 
> in
> a document (GLEP and/or Wiki page) so that confusion is avoided and we all are
> on the same page on this topic.

You start by accepting my retirement.

-- 
Best regards,
Michał Górny

[gentoo-dev] Uclibc performance

[cbergstrom]

does uclibc handle libm stuff as well like sin/cos?

If so has anyone benchmarked it? ‎I guess same question applies to memcpy and 
friends who can have a performance impact