drauschenbach opened a new issue, #6681:
URL: https://github.com/apache/arrow-rs/issues/6681

   This discussion aims to outline what would be required to add comprehensive 
support for the arm32v7 hardware architecture. Because it was in the top 3 
best-selling computers of all time, and edge hardware is likely to remain in 
service for quite some time, and because edge is a particularly strong use case 
for Arrow.
   
    And secondarily, consider how that might also benefit independent efforts 
to support WASM32.
   
   Here are some of my own ideas:
   
   1. Perform tests and clippy static checks for both amd64 and armhf. amd64 
must pass, armhf can fail until official support is completed.
   2. Tests that are specifically 64-bit in nature should not be attempted on 
32-bit platforms (use `#[cfg(target_pointer_width = "64")]` around the test 
function). The POC at #6678 outlines most of these.
   3. Scrutinize test coverage for `DecimalType`, `Decimal128Type` and 
`Decimal256Type` which do not work on armhf.
   4. Scrutinize test coverage for `Time64MicrosecondType` and 
`Time64NanosecondType`, which do not work on armhf.
   5. Consider adding a badge to the README outlining current hardware platform 
support.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to