| 1 |
Am 08/18/11 12:08, schrieb James Broadhead: |
| 2 |
> On 18 August 2011 09:23, Norman Rieß <norman@×××××××××.org> wrote: |
| 3 |
>> Am 08/18/11 09:11, schrieb Matthew Finkel: |
| 4 |
>>> Just out of curiosity, how long does it take to compile gcc? |
| 5 |
>>> |
| 6 |
>>> - Matt |
| 7 |
>> |
| 8 |
>> Atom: |
| 9 |
>> |
| 10 |
>> genlop -t sys-devel/gcc-4.4.5 |
| 11 |
>> * sys-devel/gcc |
| 12 |
>> |
| 13 |
>> Sat Feb 26 13:06:08 2011 >>> sys-devel/gcc-4.4.5 |
| 14 |
>> merge time: 1 hour, 12 minutes and 27 seconds. |
| 15 |
>> |
| 16 |
>> Wed Mar 23 23:01:12 2011 >>> sys-devel/gcc-4.4.5 |
| 17 |
>> merge time: 1 hour, 10 minutes and 22 seconds. |
| 18 |
> |
| 19 |
> I have an Atom 330 machine which is getting significantly worse |
| 20 |
> build-times than you. What make.conf options are you using? (Or are |
| 21 |
> you using something else to improve build times?) |
| 22 |
> |
| 23 |
> Wed Mar 16 04:49:09 2011 >>> sys-devel/gcc-4.4.5 |
| 24 |
> merge time: 2 hours, 56 minutes and 20 seconds. |
| 25 |
> |
| 26 |
> Thu May 5 22:07:36 2011 >>> sys-devel/gcc-4.3.4 |
| 27 |
> merge time: 2 hours, 14 minutes and 15 seconds. |
| 28 |
> |
| 29 |
> Fri May 6 00:35:53 2011 >>> sys-devel/gcc-4.4.5 |
| 30 |
> merge time: 2 hours, 28 minutes and 17 seconds. |
| 31 |
> |
| 32 |
> Admittedly, my machine runs xbmc, which is a resource hog, and has a |
| 33 |
> fair bit of disk activity. |
| 34 |
> My CFLAGS are: |
| 35 |
> CFLAGS="-O2 -march=core2 -mtune=generic -fomit-frame-pointer -pipe |
| 36 |
> -mssse3 -mfpmath=sse" |
| 37 |
> which date to before -march=atom, and having read a performance |
| 38 |
> article suggesting these. I note that the only practical difference |
| 39 |
> between the resultant gcc options is that setting -mtune to core2 adds |
| 40 |
> "#define __tune_core2__ 1". I wonder what the practical difference is. |
| 41 |
> echo | gcc -dM -E - -O2 -march=core2 -mtune=generic |
| 42 |
> -fomit-frame-pointer -pipe -mssse3 -mfpmath=sse |
| 43 |
> |
| 44 |
> I suppose, having looked into it this far, I'll merge gcc-4.5 to see |
| 45 |
> what effect -mtune=atom has. |
| 46 |
> |
| 47 |
> (I'm not particularly interested in build times, but whether they're a |
| 48 |
> sign of poor overall performance ... ) |
| 49 |
> |
| 50 |
> JB |
| 51 |
> |
| 52 |
|
| 53 |
Well i use an Atom D510, the core features seems to be quite similar to |
| 54 |
yours, with the only difference, that D510 has a graphics unit added. |
| 55 |
Here is my make.conf... how many threads are you using in gcc? |
| 56 |
|
| 57 |
CFLAGS="-O2 -pipe -march=core2 -mssse3 -mfpmath=sse" |
| 58 |
CXXFLAGS="${CFLAGS}" |
| 59 |
CHOST="x86_64-pc-linux-gnu" |
| 60 |
MAKEOPTS="-j5" |
| 61 |
|
| 62 |
USE="-X -gtk -gtk2 -qt3 -qt4 -gnome -kde unicode nls -mysql mmx sse sse2 |
| 63 |
ssse3 acpi hddtemp threads iproute2" |
| 64 |
|
| 65 |
LINGUAS="de" |
| 66 |
AUTOCLEAN="yes" |
| 67 |
FEATURES="parallel-fetch" |
| 68 |
|
| 69 |
Norman |
Archives