You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 28, 2022. It is now read-only.
Accel already implements some of the features of https://github.com/denzp/rust-ptx-linker, but it seems that the linker handles more cases (eg mangled names containing invalid characters). Could Accel simply use the linker? This would save duplicate work.
The text was updated successfully, but these errors were encountered:
It will not be simple, but I plan to switch to it.
accel/nvptx crate tried to switch from out-of-tree compile of rustc (using xargo) to in-tree compile of rustc. nvptx also contains patches of libstd (rust-accel/rust#1)
Name mangling issue is resolved in the code generation phase in accel while rust-ptx-linker resolve it on the link phase. I intend to use ptx-linker as a default linker of nvptx64-nvidia-cuda target like Cortex-M team does
Accel already implements some of the features of https://github.com/denzp/rust-ptx-linker, but it seems that the linker handles more cases (eg mangled names containing invalid characters). Could Accel simply use the linker? This would save duplicate work.
The text was updated successfully, but these errors were encountered: