-
Notifications
You must be signed in to change notification settings - Fork 50
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
Support aarch64-unknown-linux-gnu #422
Comments
Current status: Many tests crash. I arbitrarily picked uddsketch::tests::pg_uddsketch_io_test to start with. Backtrace:
|
The crash goes away when I remove the non-standard Can we just remove it? Currently rebuilding the world with This also makes me realize we publish binaries built with |
Filed ron-rs/ron#379 |
With LTO flipped back to the default of "off", I'm down to just one test failure:
|
aarch64 varies a lot more on "covar_pop" and "covar_samp". We investigated a bit and found that the postgresql equivalents we were comparing against varied further from amd64 behavior than toolkit's. Possibly differences between gcc and llvm code-gen? closes issue #422
- Raise timeout from the default of 6 hours to 12. aarch64 build seems to have been almost done when it got killed at 6 hours: it had gotten all the way to the doctester build which is almost the last step (and probably the last compiler run). A later run took only 4 hours. Still, we're emulating a CPU; cut it some slack! - Only setup QEMU for arm64 not a bunch of other platforms we don't use. - Stop setting load: true . - Stop building doctester. We've built it from source since commit 0b92688 . for issue #422
Nightly because even a null build with a warm cache takes 30 minutes just to start running the first test. for issue #422
Nightly because even a null build with a warm cache takes 30 minutes just to start running the first test. for issue #422
aarch64 varies a lot more on "covar_pop" and "covar_samp". We investigated a bit and found that the postgresql equivalents we were comparing against varied further from amd64 behavior than toolkit's. Possibly differences between gcc and llvm code-gen? for issue #422
It became "thin" in commit d18ebe6. Fixes segfaults on aarch64-unknown-linux-gnu (ron-rs/ron#379) Also drop redundant default overrides from profiles. for issue #422
aarch64 varies a lot more on "covar_pop" and "covar_samp". We investigated a bit and found that the postgresql equivalents we were comparing against varied further from amd64 behavior than toolkit's. Possibly differences between gcc and llvm code-gen? for issue #422
- Raise timeout from the default of 6 hours to 12. aarch64 build seems to have been almost done when it got killed at 6 hours: it had gotten all the way to the doctester build which is almost the last step (and probably the last compiler run). A later run took only 4 hours. Still, we're emulating a CPU; cut it some slack! - Only setup QEMU for arm64 not a bunch of other platforms we don't use. - Stop setting load: true . - Stop building doctester. We've built it from source since commit 0b92688 . for issue #422
434: Make some changes to support aarch64-unknown-linux-gnu r=epgts a=epgts - Change `lto` back to default of `false`. - It became "thin" in commit d18ebe6 . - Fixes segfaults on aarch64-unknown-linux-gnu (ron-rs/ron#379) - Change stats_agg::tests::pg_stats_agg_fuzz to allow more variance. - aarch64 varies a lot more on "covar_pop" and "covar_samp". We investigated a bit and found that the postgresql equivalents we were comparing against varied further from amd64 behavior than toolkit's. Possibly differences between gcc and llvm code-gen? - Also drop redundant default overrides from profiles in Cargo.toml . for issue #422 Co-authored-by: Eric Gillespie <epg@timescale.com>
We're seeing increased demand to support aarch64 for Linux platforms, in both private and public (e.g. issue #382). We plan to support a binary release (e.g. Docker image), but a first step is to make the toolkit work on aarch64-unknown-linux-gnu at all.
Acceptance criteria:
Out of scope:
The text was updated successfully, but these errors were encountered: