Issue 33145: unaligned accesses in siphash24() lead to crashes on sparc - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
process
Status: closed Resolution: duplicate
Dependencies: Superseder: pyhash's siphash24 assumes alignment of the data pointer
View: 28055
Assigned To: Nosy List: Dakon, Jeffrey.Walton, serhiy.storchaka
Priority: normal Keywords:

Created on 2018-03-26 16:29 by Dakon, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 6123 Dakon, 2018-03-26 16:29
Messages (2)
msg314464 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2018-03-26 16:52 
Actually this looks like a duplicate of issue28055.
msg322096 - (view) Author: Jeffrey Walton (Jeffrey.Walton) * Date: 2018-07-21 12:24 
I know this is a bit late but I wanted to share...

OpenCSW has a build farm with Solaris machines and Sparc hardware. The farm provides x86 and Sparc machines with Solaris 9 through 11.

I believe OpenCSW operates in the same spirit as GCC compile farm. They welcome open source developers and upstream maintainers to help ensure packages build and run on Solaris machines.

You can read about it at
https://www.opencsw.org/extend-it/signup/to-upstream-maintainers/ .

If Python is performing memory access patterns as discussed in the report then it would probably benefit the project to test on a Sparc machine with Solaris 11.