Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com added the comment:
I think that this change could be backported to 3.1 branch. It doesn't cause
any additional warnings, which are absent in py3k branch (see issue #8623).
r79499 doesn't merge cleanly, so I'm attaching the patch for
Benjamin Peterson benja...@python.org added the comment:
2010/6/21 Arfrever Frehtes Taifersar Arahesis rep...@bugs.python.org:
Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com added the
comment:
I think that this change could be backported to 3.1 branch. It doesn't cause
any
Daniel Stutzbach dan...@stutzbachenterprises.com added the comment:
Attached is a patch for configure.in and configure that implements Benjamin's
suggestion. The patch sets things up to continue to use -fno-strict-aliasing
on gcc versions that support -fno-strict-aliasing *and* generate
Benjamin Peterson benja...@python.org added the comment:
Thanks for the patch. Applied in r79499.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3326
Benjamin Peterson benja...@python.org added the comment:
I propose that we remove -fno-strict-aliasing for gcc = 4.3.
--
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3326
Daniel Stutzbach dan...@stutzbachenterprises.com added the comment:
I'm using gcc 3.4.4 (cygwin) and I get the sames warnings as Alexandre.
I examined a random sampling of the code generating the warnings, all of
which followed this pattern:
some_function((some_type **)
Alexandre Vassalotti [EMAIL PROTECTED] added the comment:
With gcc 4.2.3, I see a whole bunch of warnings:
Objects/exceptions.c: In function ‘UnicodeDecodeError_init’:
Objects/exceptions.c:1472: warning: dereferencing type-punned pointer
will break strict-aliasing rules
Objects/frameobject.c:
Ismail Donmez [EMAIL PROTECTED] added the comment:
Wow thats no good, I will test with -fstrict-aliasing to be sure, if there
are such problems still we should start with fixing those towards 3.1 .
___
Python tracker [EMAIL PROTECTED]
New submission from Ismail Donmez [EMAIL PROTECTED]:
py3k branch is still using -fno-strict-aliasing but I tested with gcc
4.3.1 and there are no strict aliasing warnings when this flag is removed.
Attached patch for py3k branch removes this flag. After applying the
patch configure should be
