Exploration

[Jasper-Bekkers]

• Need to structurize control flow to insert OpLoopMerge / OpSelectionMerge: Question: why OpSelectionMerge and OpLoopMerge are separate instructions? KhronosGroup/SPIRV-Headers#147
• Need phi-node insertion (might be able to take that from llvm-> spirv translator)

[khyperia]

Some very high level tasks, in vague order of implementation order:

1. Create infrastructure for emitting a module, i.e. wiring the rspirv context module through function emission, and emit the file at the end of compilation.
2. Start on the guts of the codegen, e.g. start off with a big ol' match statement that translates the simple things, that slowly gets filled out.
3. Create testing framework, e.g. a way to ergonomically write "here's some rust, I expect this spirv".
4. Implement multi-crate support. I imagine this means writing a spirv linker, taking the spirv output of dependent libs and linking it into the current crate?
5. Design an ergonomic way to use the project. This is a whole brainstorm, but for example, have users specify in a build.rs a path to a crate, and it outputs a file that you can include_bytes! or whatever.
6. Extension of step 2, actually implement the complex codegen scenarios. Make sure everything works. Do complex compilery stuff, e.g. if we want to mem2reg the output (phi nodes), stuff like that. I imagine 90% of the project time will be here.
7. Publish to the world!

[MarnixKuijs]

5. Design an ergonomic way to use the project. This is a whole brainstorm, but for example, have users specify in a build.rs a path to a crate, and it outputs a file that you can include_bytes! or whatever.

the rust cuda ecosystem has something like this (https://crates.io/crates/ptx-builder). All you have to specify in a build.rs file is:

use ptx_builder::error::Result;
use ptx_builder::prelude::*;

fn main() -> Result<()> {
    let builder = Builder::new(".")?;
    CargoAdapter::with_env_var("KERNEL_PTX_PATH").build(builder);
}

which allows a user to get the contents of their ptx file through:

let ptx_file = CString::new(include_str!(env!("KERNEL_PTX_PATH"))).unwrap();

I'm currently doing some research to see how it works

[khyperia]

We've mostly already implemented things in this issue, and it's mostly been replicated in #47, so closing this.