On 08/19/2011 02:04 AM, Richard Guenther wrote: > So make sure that __cpu_indicator initially has a conservative correct > value? I'd still prefer the constructor-in-libgcc option - if only because > then the compiler-side is much simplified. >
Err, I thought __cpu_indicator was a function, not data. I think we need to discuss this more... r~