Open Bug 1503150 Opened 3 years ago Updated 3 months ago

Merge Chromium change to zlib for arm optimization

Categories

(Core :: JavaScript Engine, enhancement, P2)

ARM
Android
enhancement

Tracking

()

Tracking Status
firefox65 --- affected

People

(Reporter: m_kato, Assigned: m_kato)

References

(Blocks 1 open bug)

Details

From https://bugs.chromium.org/p/chromium/issues/detail?id=709716

Although zlib doesn't include Google's patch, as long as I read http://crbug.com/709716, it is good for performance for cortex-A53/57/7x devices.

So we consider merge this change to Gecko.
Not sure SpiderMonkey is a better place for this bug but General didn't seem great, either ...
Component: General → JavaScript Engine
Priority: -- → P2
Assignee: nobody → m_kato

There's also CloudFlare's zlib https://github.com/cloudflare/zlib which includes crc32 optimization for aarch64 and amd64 and a bunch of other general optimizations. Doesn't include adler32 simd optimization, which google has I think

(In reply to greg v [:myfreeweb] from comment #2)

There's also CloudFlare's zlib https://github.com/cloudflare/zlib which includes crc32 optimization for aarch64 and amd64 and a bunch of other general optimizations. Doesn't include adler32 simd optimization, which google has I think

I think that zlib-ng is better solution rather than google's patch or couldflare's patch. But zlib-ng isn' still stable. After it has release version, I consider it.

(In reply to Makoto Kato [:m_kato] from comment #3)

I think that zlib-ng is better solution rather than google's patch or couldflare's patch. But zlib-ng isn' still stable. After it has release version, I consider it.

Yes, looks like zlib-ng does merge all the optimizations, very nice.

zlib-ng has had a few releases already by now: https://github.com/zlib-ng/zlib-ng/releases

You need to log in before you can comment on or make changes to this bug.