Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IBM S390X contrib cleanup #1050

Open
8 tasks
fneddy opened this issue Feb 25, 2025 · 0 comments
Open
8 tasks

IBM S390X contrib cleanup #1050

fneddy opened this issue Feb 25, 2025 · 0 comments

Comments

@fneddy
Copy link

fneddy commented Feb 25, 2025

The Problem

the zlib accelerators for the IBM S390X (and IBM POWER) platform is in an unclean state. For the sake of easier patch generation for Linux distributions and potential merge into mainline zlib this should be cleaned up.

Analysis

the current open PR #410 is based on the work of the IBM POWER optimization #750. The Power work itself fragmented in the last years into 6 different PRs ( #857 #750 #478 #459 #458 #457 tracked in #847).

The S390X PR has multiple problems:

  • it needs rebaseing on the newest development branch.
  • it uses ifunc that causes problems with memory sanitizers and musl(critical for alpine linux).
  • the CI only runs for configure
  • the cmake build does not include the S390X accelerators
  • the CI only runs with QEMU. QEMU has actually no support for the instructions used in the optimization and zlib will fall back on testing the software implementation.
  • no dedicated crc32 test cases

Tracking

To get the S390X code in the clean state this are the issues and milestones that need to be solved.

I started working on this issues in my fork and will create PR(s) when i think they are ready. I work closely with @iii-i to cleanup and refine the code. Also I talked with a POWER dev and they state their interest in cleaning up their part.

Footnotes

  1. There are free native IBM S390X workers for open source projects from Marist University

  2. I need input if and under what circumstances the code could be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant