`entry_point_name` should be decoupled from the output file name
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.4k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
When using something like this
#[spirv(fragment(entry_point_name = "main"))]
main_frag(){}
I expect output to be main_frag.spv with an OpEntryPoint of "main". Instead, I am seeing cargo gpu using entry_point_name for the output file name. This means I can't decouple them.
I need to decouple as I have a multishader, so I need to output unique file names to know which shader is which. I am running in a harness I don't control that expects "main" for all shader entry points.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing cargo gpu's output filename handling for the entry_point_name attribute. Add a regression test covering a function such as main_frag with entry_point_name = "main"; done means the output file uses the function name while the SPIR-V OpEntryPoint retains "main".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100