-
Notifications
You must be signed in to change notification settings - Fork 250
Update to nightly-2022-10-15 #954
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, the only addressable comment would be the one about not passing None
(it might not matter now but we wouldn't want weird bugs in the future if we start relying on it).
EDIT: oops, you pushed the change in tests, which will definitely break at least 4 of them (try running cargo test -p rustc_codegen_spirv --lib
to see what I mean).
bx.call(entry_func.ty, entry_func, &call_args, None); | ||
bx.call(entry_func.ty, None, entry_func, &call_args, None); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can pass Some
if you change this function (shader_entry_stub
) to take the whole FnAbi
(and call it entry_fn_abi
) instead of arg_abis
(which is the .args
field of that very FnAbi
).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happened here? I see thumbs up but also marked as resolved and no change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks ready but I'm not sure if you want to pass Some(entry_fn_abi)
from that entry.rs
function or not.
bx.call(entry_func.ty, entry_func, &call_args, None); | ||
bx.call(entry_func.ty, None, entry_func, &call_args, None); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happened here? I see thumbs up but also marked as resolved and no change?
Opened a PR to move us off of |
Apparently forgot to use the param in the actual call 😬 |
The new
fn_abi
parameter inBuilderMethods::call()
andinvoke()
scares me a bit. Here's the relevant PR in rust-langTests pass and examples run.
With 2022-10-29 we're up to date for the new Rust 1.66 stable that's going to be released on Dec 15.
EDIT Back to 10-15 because of a blocked issue (
diagnostic_output
being removed fromConfig
)