Gentoo Archives: gentoo-dev

From: Peter Hjalmarsson <xake@×××××××××.net>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: Re: [gentoo-commits] gentoo-x86 commit in dev-python/traits: traits-3.4.0.ebuild
Date: Sun, 20 Jun 2010 16:05:48
Message-Id: 1277049908.22112.16.camel@lillen
In Reply to: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/traits: traits-3.4.0.ebuild by Arfrever Frehtes Taifersar Arahesis
1 sön 2010-06-20 klockan 15:55 +0200 skrev Arfrever Frehtes Taifersar
2 Arahesis:
3 >
4 > This problem is probably caused by bugs in Python 2, which have been fixed in Python 3.
5 >
6 > $ echo 'a = True' > test.pyx
7 > $ cython test.pyx
8 > $ gcc -O2 -Wall -I/usr/include/python3.1 -c test.c
9 > $ gcc -O2 -Wall -I/usr/include/python2.6 -c test.c
10 > test.c: In function ‘inittest’:
11 > test.c:479: warning: dereferencing type-punned pointer will break strict-aliasing rules
12 > test.c:479: warning: dereferencing type-punned pointer will break strict-aliasing rules
13 > test.c:479: warning: dereferencing pointer ‘_Py_TrueStruct.42’ does break strict-aliasing rules
14 > test.c:479: warning: dereferencing pointer ‘_Py_TrueStruct.42’ does break strict-aliasing rules
15 > test.c:479: note: initialized from here
16 > test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break strict-aliasing rules
17 > test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break strict-aliasing rules
18 > test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break strict-aliasing rules
19 > test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break strict-aliasing rules
20 > test.c:479: note: initialized from here
21 >
22
23 Actually this makes me question the append-flag even more.
24 Why mess with what gcc does with the code for all versions of python if
25 it works for x version of python?
26 And "only" for som warnings? I could have understand a bit more if it
27 was Errors.
28
29 Also why not even a comment saying?
30
31 Currently as one of the users of hardened and helping Zorry out with the
32 hardened toolchain I have seen many packages filter flags like -fPIE and
33 -fstack-protector without a comment on why, where and how it broke, and
34 noone remeber why.
35 New versions comes of software and if you do not know why it broke with
36 a cflag you cannot test if the breakage is still there.
37
38 This line of code is fine and all that until you forget why you added
39 that flag or you retire and a later maintainer of the package does not
40 dare to touch the flag since they do not know why it was added and what
41 will break if the remove that line of ebuild code.