1 |
Hi list! |
2 |
|
3 |
I'm wondering how to interpret the custom-optimization use flag which |
4 |
has become much more common in the recent weeks/months. |
5 |
|
6 |
I mean, I understand the basic concept: it either uses the cflags from |
7 |
my make.conf or its own set. But what exactly does the dev want to tell |
8 |
me when she uses this flag and sets it to default off? |
9 |
|
10 |
1. "If you have a fancy set of uncommon cflags, this package might break |
11 |
in funny ways. Therefore you might want to use my set of conservative |
12 |
flags instead." |
13 |
|
14 |
2. "In order to run perfectly, this package needs a very unique set of |
15 |
cflags. Trust me to set them properly if you have a rather common system." |
16 |
|
17 |
3. "No one will give you support when this package breaks unless you use |
18 |
the default compile flags. However, for optimal performance you might |
19 |
still want to use your own set of flags." |
20 |
|
21 |
I'm asking because very different packages have started using this flag, |
22 |
for example Firefox and ffmpeg. For Firefox, I'd think the dev thought |
23 |
of 1 or 3. With ffmpeg, number 2 might be the right interpretation, |
24 |
especially as it seems to set such uncommon flags as -O3 (which always |
25 |
decreased performance when I tried it for other packages or my own |
26 |
programs). |
27 |
|
28 |
Just for the records: I'm using a conservative set of cflags: |
29 |
-march=core2 and -O2 |