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
I've recently started working on nvptx support in Rust and has run into the problem of not being able to use ptx-linker in assembly tests.
The ptx-linker used to be active in the rustc but was removed in f8f9a2869cce570c994d96afb82f4162b1b44cca. It seems to me like the issue is fixed (in denzp/rustc-llvm-proxy#7), and there is no reason to not add it back and enable nvptx tests, is this correct? If not, what can I do to help the situation? (Relevant discussion here to jog the memory rust-lang/rust#59752)
Looking even further in the future. What is the ideal way to distribute ptx-linker? I imagine it would be better to somehow distribute it together with the nvptx64 toolchain in rustup? Are there anything that can help the situation right now, or is it basically waiting for more rust ptx adoption?
The text was updated successfully, but these errors were encountered:
I've recently started working on nvptx support in Rust and has run into the problem of not being able to use ptx-linker in assembly tests.
The
ptx-linker
used to be active in therustc
but was removed in f8f9a2869cce570c994d96afb82f4162b1b44cca. It seems to me like the issue is fixed (in denzp/rustc-llvm-proxy#7), and there is no reason to not add it back and enable nvptx tests, is this correct? If not, what can I do to help the situation? (Relevant discussion here to jog the memory rust-lang/rust#59752)Looking even further in the future. What is the ideal way to distribute ptx-linker? I imagine it would be better to somehow distribute it together with the nvptx64 toolchain in rustup? Are there anything that can help the situation right now, or is it basically waiting for more rust ptx adoption?
The text was updated successfully, but these errors were encountered: