4 ms·

There's probably something that'll break, but iOS switched to 16KB pages with zero publicity or warning and it caused very few problems. The vast majority of ap

There's probably something that'll break, but iOS switched to 16KB pages with zero publicity or warning and it caused very few problems. The vast majority of applications don't care about what the page size is at all, and cross-platform native code already has to handle different page sizes so hopefully people didn't do the stupid thing of hardcoding it for Android and only dynamically checking on iOS.

comex 1y ago
Isn’t the biggest issue that compiled binaries have segments aligned only to 4kb, and those segments must be on different pages (because they have different memory protections) and can’t be slid relative to each other? I’m not sure how iOS dealt with this (maybe arm64 binaries always had 16kb aligned segments?), but apparently this is an issue on Android and requires all binaries to be recompiled. https://source.android.com/docs/core/architecture/16kb-page-size/16kb https://source.android.com/docs/core/architecture/16kb-page-...
- pjmlp 1y ago
  The NDK is a well of surprises, when I used to do Android native, I always thought it was a kind of 20% project at Google.
- gsnedders 1y ago
  > maybe arm64 binaries always had 16kb aligned segments? Yes — because the move to 16k pages happened at the same time as the move to arm64.