| 1 |
On Wed, Nov 16, 2011 at 2:11 AM, Stéphane Guedon <stephane@××××××××××.eu> wrote: |
| 2 |
> On Wednesday 16 November 2011 02:07:12 Pandu Poluan wrote: |
| 3 |
>> And if you're adventurous, add USE "graphite", reemerge gcc, and reemerge |
| 4 |
>> world :) |
| 5 |
> |
| 6 |
> what does "graphite" add ? |
| 7 |
|
| 8 |
Thanks for reminding me; I meant to look it up when I got home. |
| 9 |
|
| 10 |
shortcircuit:1@serenity~ |
| 11 |
Wed Nov 16 02:16 AM |
| 12 |
!501 #1 j0 ?0 $ euse -i graphite |
| 13 |
global use flags (searching: graphite) |
| 14 |
************************************************************ |
| 15 |
no matching entries found |
| 16 |
|
| 17 |
local use flags (searching: graphite) |
| 18 |
************************************************************ |
| 19 |
|
| 20 |
[snip] |
| 21 |
|
| 22 |
[- ] graphite |
| 23 |
sys-devel/gcc: Add support for the framework for loop optimizations |
| 24 |
based on a polyhedral intermediate representation |
| 25 |
|
| 26 |
So, a new, experimental optimization model and framework inside your |
| 27 |
compiler. If it's specifically for optimizing on loops, I'll venture a |
| 28 |
guess it's going to be mostly effective for graphics libraries and |
| 29 |
apps. I've got some slightly riskier educated guesses on how it works |
| 30 |
and what some numeric side effects and consequences might be, but they |
| 31 |
scare me, so I think I'll leave it to someone who actually knows more |
| 32 |
about it... |
| 33 |
|
| 34 |
-- |
| 35 |
:wq |
Archives