On Sat, Apr 26, 2014 at 10:37 PM, "C. Bergström"
wrote:
> #2 The only reference to anything which the compiler could impact is
> "Use Boyer-Moore (and unroll its inner loop a few times)." Finding out which
> flag controls that for ${CC} would have some importance. It's almost
> certainly combined
On 04/27/14 06:23 PM, Rich Freeman wrote:
On Sat, Apr 26, 2014 at 10:37 PM, "C. Bergström"
wrote:
#2 The only reference to anything which the compiler could impact is
"Use Boyer-Moore (and unroll its inner loop a few times)." Finding out which
flag controls that for ${CC} would have some import
On Sun, Apr 27, 2014 at 7:41 AM, "C. Bergström"
wrote:
> On 04/27/14 06:23 PM, Rich Freeman wrote:
>> And yet, in the same paragraph you mention -O3, which is tantamount to
>> just setting a flag and walking away. That turns on 14 things you
>> probably don't really need.
>
> I was trying to give
On 04/27/2014 07:23, Rich Freeman wrote:
> On Sat, Apr 26, 2014 at 10:37 PM, "C. Bergström"
> wrote:
>> #2 The only reference to anything which the compiler could impact is
>> "Use Boyer-Moore (and unroll its inner loop a few times)." Finding out which
>> flag controls that for ${CC} would have so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
# Manuel Rüger (28 Apr 2014)
# Fails to build with gnutls-3, on behalf of python herd
# See bug #446016
dev-python/python-gnutls
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enig
On 04/26/2014 20:34, "C. Bergström" wrote:
> On 04/27/14 02:58 AM, Martin Vaeth wrote:
>> Rich Freeman wrote:
>>> FWIW the list of packages I have issues with include:
>> Not sure whether this is the right place to post it.
> It's interesting to see that rather lengthy list. From a compiler engine
On Sun, Apr 27, 2014 at 6:56 PM, Joshua Kinard wrote:
>
> My curiosity, as I have not attempted LTO yet on any machine, is what are
> the RAM requirements? Is it a hard limit, wherein the compiler simply fails
> if there isn't enough RAM, or does it just start hitting swap real hard?
It just all
On 04/27/2014 19:08, Rich Freeman wrote:
> On Sun, Apr 27, 2014 at 6:56 PM, Joshua Kinard wrote:
>>
>> My curiosity, as I have not attempted LTO yet on any machine, is what are
>> the RAM requirements? Is it a hard limit, wherein the compiler simply fails
>> if there isn't enough RAM, or does it
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2014-04-27 23h59 UTC.
Removals:
x11-themes/faenza-xfce-icon-theme 2014-04-23 08:26:52 ssuominen
dev-qt/linguist-tools 2014-04-23 10:48:16 zlogene
dev-qt/qttrans
On 04/28/14 06:14 AM, Joshua Kinard wrote:
On 04/27/2014 19:08, Rich Freeman wrote:
On Sun, Apr 27, 2014 at 6:56 PM, Joshua Kinard wrote:
My curiosity, as I have not attempted LTO yet on any machine, is what are
the RAM requirements? Is it a hard limit, wherein the compiler simply fails
if th
On 04/27/2014 20:40, "C. Bergström" wrote:
> On those old SGI MIPS machines use MIPSPro. It had better (LTO/whole
> program) optimizations than GCC more than 10 years ago (imho and gcc may
> have caught up now in 4.9). Just add the -ipa flag and test. In fairness
> there is primarily 3 limitations
On Sun 27 Apr 2014 08:40:08 PM EDT, "C. Bergström" wrote:
> In terms of general performance gains using LTO - The #1 candidate
> would be the linux kernel actually. See if anyone can get that to work ;)
Intel's Andi Kleen is working on it:
http://lkml.iu.edu/hypermail/linux/kernel/1404.0/03450.ht
Robin H. Johnson:
> Removals:
[...]
> dev-qt/linguist-tools 2014-04-23 10:48:16 zlogene
> dev-qt/qttranslations 2014-04-23 10:49:23 zlogene
> dev-qt/qtquick1 2014-04-23 11:10:31 zlogene
> dev-qt/qtnetwork 2014-04
13 matches
Mail list logo
