[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-09 Thread Matthias Klose
Changes by Matthias Klose : Added file: http://bugs.python.org/file44515/pyhash.diff ___ Python tracker <http://bugs.python.org/issue28055> ___ ___ Python-bugs-list mailin

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-09 Thread Matthias Klose
Changes by Matthias Klose : Removed file: http://bugs.python.org/file44514/pyhash.diff ___ Python tracker <http://bugs.python.org/issue28055> ___ ___ Python-bugs-list m

[issue28027] Remove Lib/plat-*/* files

2016-09-09 Thread Matthias Klose
Matthias Klose added the comment: "It's a matter of maintenance burden". No I don't think so. As agreed on IRC with zware, I'll restore the removed modules, including a deprecation notice. -- assignee: zach.ware -> doko resolution: fixe

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-10 Thread Matthias Klose
Matthias Klose added the comment: I don't like that configure check, because it depends on the kernel being used at runtime. For many architectures you can define in the kernel if the kernel should allow unaligned accesses or not. Sure this is not an issue for linux distro builds, but

[issue28046] Remove the concept of platform-specific directories

2016-09-13 Thread Matthias Klose
Matthias Klose added the comment: I don't like the _PYTHON_SYSCONFIGDATA_NAME hack. This should be based on the target, not on a name for just a particular file. Following up on that in #28125. -- ___ Python tracker <http://bugs.py

[issue28125] identify cross builds by a more generic environment setting.

2016-09-13 Thread Matthias Klose
New submission from Matthias Klose: I don't like the _PYTHON_SYSCONFIGDATA_NAME hack introduced in #28046. This should be based on the target, not on a name for just a particular file. Plus the abi flags should not be set by hand, you'll get in trouble at least for naming exte

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-13 Thread Matthias Klose
Matthias Klose added the comment: updated patch that always used memcpy for the little endian case. -- Added file: http://bugs.python.org/file44628/pyhash.diff ___ Python tracker <http://bugs.python.org/issue28

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-13 Thread Matthias Klose
Changes by Matthias Klose : Removed file: http://bugs.python.org/file44515/pyhash.diff ___ Python tracker <http://bugs.python.org/issue28055> ___ ___ Python-bugs-list m

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-13 Thread Matthias Klose
Changes by Matthias Klose : Removed file: http://bugs.python.org/file44628/pyhash.diff ___ Python tracker <http://bugs.python.org/issue28055> ___ ___ Python-bugs-list m

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-13 Thread Matthias Klose
Changes by Matthias Klose : Added file: http://bugs.python.org/file44629/pyhash.diff ___ Python tracker <http://bugs.python.org/issue28055> ___ ___ Python-bugs-list mailin

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-13 Thread Matthias Klose
Matthias Klose added the comment: a variant of the patch that keeps the parameter types of _le64toh. -- Added file: http://bugs.python.org/file44630/pyhash2.diff ___ Python tracker <http://bugs.python.org/issue28

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-13 Thread Matthias Klose
Matthias Klose added the comment: I can check, if the memcpy is optimized away. As an alternative, we could use __builtin_memcpy. That is available for clang as well (would have to check icc). -- ___ Python tracker <http://bugs.python.

[issue28125] identify cross builds by a more generic environment setting.

2016-09-13 Thread Matthias Klose
Matthias Klose added the comment: On 13.09.2016 16:40, Xavier de Gaye wrote: > > Xavier de Gaye added the comment: > >> Plus the abi flags should not be set by hand, you'll get in trouble at least >> for naming extensions, or building extensions for the wrong

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-13 Thread Matthias Klose
Matthias Klose added the comment: > I believe the unaligned memory access configure check is supposed to > prevent siphash from being used, so we might look into why that's not > working. > > IMO, though, we should just require alignment for the argument to > _PyHash_By

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-13 Thread Matthias Klose
Matthias Klose added the comment: ... would be to remove the autoconf check and make the selection of the hash method unconditional ... -- ___ Python tracker <http://bugs.python.org/issue28

[issue28125] identify cross builds by a more generic environment setting.

2016-09-13 Thread Matthias Klose
Matthias Klose added the comment: On 13.09.2016 23:43, Xavier de Gaye wrote: > > Xavier de Gaye added the comment: > > You do not answer my questions and resort to sarcasm instead: "How did you > make it more difficult?". I understand that you may be upset becaus

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-13 Thread Matthias Klose
Matthias Klose added the comment: if the only concern is 32bit sparc, then please let's drop this in 3.6. Looking at #28027 the new way to obsoleting things seems to be decreeing them (sorry about the sarcasm). If I interpret your concerns correctly you care about platforms, which yo

[issue28055] pyhash's siphash24 assumes alignment of the data pointer

2016-09-13 Thread Matthias Klose
Changes by Matthias Klose : -- nosy: +gvanrossum, ned.deily ___ Python tracker <http://bugs.python.org/issue28055> ___ ___ Python-bugs-list mailing list Unsub

[issue28167] remove platform.linux_distribution()

2016-09-15 Thread Matthias Klose
New submission from Matthias Klose: platform.linux_distribution() was deprecated in 3.5, and should be removed. Can't be kept up to date, see #18872, #19213, #20454, #1180267, plus uncounted issues closed as won't fix. I'm surprised that #26041 removed the removal warnings aga

[issue28190] Detect curses headers correctly for cross-compiling

2016-09-26 Thread Matthias Klose
Matthias Klose added the comment: looks good to me, thanks for working on this. -- ___ Python tracker <http://bugs.python.org/issue28190> ___ ___ Python-bug

[issue28413] unprefixed global symbol freegrammar

2016-10-10 Thread Matthias Klose
New submission from Matthias Klose: changeset 103932 introduced an unprefixed global symbol freegrammar. Please make it local, or prefix it with _Py_. -- messages: 278463 nosy: benjamin.peterson, doko priority: normal severity: normal stage: needs patch status: open title: unprefixed

[issue28468] Add platform.linux_os_release()

2016-10-18 Thread Matthias Klose
Matthias Klose added the comment: -1 This is not available everywhere, not even on Linux distributions. Why would you implement something which only works on 50% of existing Linux distributions? Who would even use that? And for what would you use it? You have a distro module available now

[issue28468] Add platform.linux_os_release()

2016-10-18 Thread Matthias Klose
Matthias Klose added the comment: "Since all major Linux distribution now use systemd, it makes sense to me to add such function." I'm not aware of any embedded Linux distro using systemd (no, I don't consider Raspian an e

[issue28468] Add platform.linux_os_release()

2016-10-18 Thread Matthias Klose
Matthias Klose added the comment: "The name of the function clearly indicats that the function only works on Linux with a os-release file." No, it does not. That would be linux_distribution_with_os_release_file(). -- ___ Python trac

[issue28401] Don't support the PEP384 stable ABI in pydebug builds

2016-10-27 Thread Matthias Klose
Matthias Klose added the comment: I'm not sure that you really want this, because it would make it impossible to build an extension for the stable ABI for a debug build. The problem is Debian specific, because we install the extension modules for normal and debug builds in the same loc

[issue28631] [2.7/3.5/3.6 Regression] crash using ctypes

2016-11-07 Thread Matthias Klose
New submission from Matthias Klose: the following example started to segfault with the 2.7 branch 20161103, last working one 20160901, on 3.5 branch 20161103, last working one 20160922. from __future__ import print_function import ctypes import ctypes.util lib_location

[issue28631] [2.7/3.5/3.6 Regression] crash using ctypes

2016-11-14 Thread Matthias Klose
Matthias Klose added the comment: closing -- resolution: -> not a bug status: open -> closed ___ Python tracker <http://bugs.python.org/issue28631> ___ ___

<    4   5   6   7   8   9