Hi Arrow Devs,
I'm a maintainer from a project called cuDF (https://github.com/rapidsai/cudf.git ), that is based on the Arrow columnar format and depends on the Arrow C++ and Python libraries. We are currently pinned to `1.0.1` and when previously tried upgrading to `3.0.0` we ran into and fixed the following issue: https://issues.apache.org/jira/browse/ARROW-11872 , and thus waited for `4.0.0` for a release with that fix included. But, upon testing the recent arrow release with recently released nvcc 11.2+ compilers, when the arrow headers are compiled with `nvcc` there is a segfault as explained in this issue: https://issues.apache.org/jira/browse/ARROW-12663 . A fix for this issue from compiler side is being worked on by our compiler teams at NVIDIA but meanwhile to have arrow support for 11.2+, we initiated a work-around in arrow that is now merged: https://github.com/apache/arrow/pull/10257. We are waiting to upgrade our project to arrow `4.0.0`, but due to the latest `nvcc` having a segfault we aren't able to upgrade. With the current arrow `master` branch we don't see any blockers, so would it be possible to do a patch release for `4.x` that includes the above compiler workaround(https://github.com/apache/arrow/pull/10257 ) ? This would greatly help us upgrade to the latest arrow version and directly help users using both Arrow and cuDF. We would also be happy to try to add a test in Arrow CI that will compile arrow headers using `nvcc` to try to prevent this type of issue moving forward. Regards, Prem
