1 |
On Wed, Nov 15, 2017 at 1:22 AM, Jorge Almeida <jjalmeida@×××××.com> wrote: |
2 |
> On Tue, Nov 14, 2017 at 8:42 PM, R0b0t1 <r030t1@×××××.com> wrote: |
3 |
>> What I am wondering about is if C code which uses |
4 |
>> __attribute__((optimize(...))) is against Gentoo package standards and |
5 |
>> would have to be removed from the Portage tree. |
6 |
>> |
7 |
> |
8 |
> |
9 |
> You can set your optimization preferences in make.conf, and still an |
10 |
> ebuild will override them if deemed unsafe. What would be the |
11 |
> difference? |
12 |
> |
13 |
|
14 |
Ebuilds are not supposed to do this, so if you file a bug report |
15 |
citing that ebuild changes will be made (eventually?) to work around |
16 |
it. |
17 |
|
18 |
|
19 |
On Wed, Nov 15, 2017 at 9:28 AM, Grant Edwards |
20 |
<grant.b.edwards@×××××.com> wrote: |
21 |
> On 2017-11-15, R0b0t1 <r030t1@×××××.com> wrote: |
22 |
> |
23 |
>> What I am wondering about is if C code which uses |
24 |
>> __attribute__((optimize(...))) is against Gentoo package standards and |
25 |
>> would have to be removed from the Portage tree. |
26 |
> |
27 |
> Huh? |
28 |
> |
29 |
> Gentoo enforces standards for the source code of packages? |
30 |
> |
31 |
> "They" review the source code for the Linux kernel, Gnome, KDE, Qt, |
32 |
> Chrome, Firefox, GCC, and 24670 thousand other packages and make sure |
33 |
> they all follow Gentoo coding standards? |
34 |
> |
35 |
|
36 |
To be consistent they would have to. Why I bring it up is that a |
37 |
number of optimizations in eix were removed due to the logic I gave |
38 |
above, despite there being no way to enable them without setting "-O3" |
39 |
globally. |
40 |
|
41 |
Cheers, |
42 |
R0b0t1 |