| 1 |
On 04/30/2017 05:04 PM, J. Roeleveld wrote: |
| 2 |
> On Sunday, April 30, 2017 2:18:42 PM CEST Nikos Chantziaras wrote: |
| 3 |
>> On 04/30/2017 05:25 AM, Walter Dnes wrote: |
| 4 |
>>> So much for that wiki entry. BTW, I ended up putting... |
| 5 |
>>> |
| 6 |
>>> sys-devel/gcc graphite |
| 7 |
>>> |
| 8 |
>>> ...in package.use. The "graphite" USE flag means something entirely |
| 9 |
>>> different for harfbuzz, i.e. build against media-libs/harfbuzz against |
| 10 |
>>> media-gfx/graphite2 |
| 11 |
>> |
| 12 |
>> Btw, I don't think that USE flag is useful for anything, unless you put |
| 13 |
>> the graphite optimization flags in your CFLAGS (-floop-interchange |
| 14 |
>> -floop-strip-mine -floop-block). If you don't use those, there shouldn't |
| 15 |
>> be a reason to enable the graphite flag. |
| 16 |
> |
| 17 |
> |
| 18 |
> Is there any benefit from using graphite and these CFLAGS on a current Gentoo |
| 19 |
> system? |
| 20 |
> |
| 21 |
> Using a simple google-search, I can't find anything recent. |
| 22 |
|
| 23 |
What Rasmus said, but the differences aren't going to be noticeable in |
| 24 |
general use. For heavy number crunching (like video encoding) or huge |
| 25 |
batch jobs or high-traffic servers maybe, but for normal desktop PC use |
| 26 |
there's not going to be a difference. |
Archives