1 |
Dirkjan Ochtman posted on Sat, 11 Dec 2010 20:03:39 +0100 as excerpted: |
2 |
|
3 |
> On Sat, Dec 11, 2010 at 20:01, Matt Turner <mattst88@g.o> wrote: |
4 |
>> I agree that this could be better. To me, most of the problems with |
5 |
>> this are due to users not knowing which of these should be set for |
6 |
>> their particular CPU. |
7 |
>> |
8 |
>> Instead of having defaults set by a profile, I'd like to figure out a |
9 |
>> way we can have these flags set by default dependent on the user's CPU. |
10 |
>> This might require some additional logic in portage; I don't know. |
11 |
> |
12 |
> Yeah, I think setting the best possible default is important here. |
13 |
|
14 |
FWIW, I don't think that's a good idea -- at least if you're suggesting |
15 |
real-time build-machine detection (see below for the alternative). Not |
16 |
only will implementing it be a lot of work, but then you'll have people |
17 |
filing bugs because they intended to compile for several different |
18 |
machines and set generic CFLAGS accordingly, but still ended up with |
19 |
broken packages because the default CPU extensions logic looked at the |
20 |
build machine only, and they thought they were done when they set the |
21 |
profile, CFLAGS and CHOST to the level of generic they intended. |
22 |
|
23 |
Unless the logic is based on the -march set in C(XX)FLAGS. That could |
24 |
work, as people should already be setting that as specific or generic as |
25 |
they want. |
26 |
|
27 |
I do like the USE_EXPAND idea, tho. |
28 |
|
29 |
Meanwhile, would it be possible to have altivec in the same USE_EXPAND? |
30 |
It's the same CPU extensions type of thing on PPC, if I'm not mistaken. |
31 |
Does profile-mask work for USE_EXPAND? Because it just seems strange to |
32 |
me to see all those CPU extensions in their own USE_EXPAND and see altivec |
33 |
still in USE. |
34 |
|
35 |
-- |
36 |
Duncan - List replies preferred. No HTML msgs. |
37 |
"Every nonfree program has a lord, a master -- |
38 |
and if you use the program, he is your master." Richard Stallman |