cbuffer shared across modules breaks precompiled dxil support

[cheneym2]

cbuffer shared across modules breaks precompiled dxil support

[cheneym2]

According to Yong in offline discussion, globals are a can of worms, implying this is at least a medium or large size task.

[cheneym2]

One consideration is whether this can be worked around with globals passed as function parameters.

[cheneym2]

Yong He
14 minutes ago
We have concluded that we won't deal with global variables previously, right?

Adam Cheney
14 minutes ago
I thought it was just deferred.

NEW

Yong He
14 minutes ago
So let's not work on this.

Yong He
13 minutes ago
spirv has higher priority.

Adam Cheney
13 minutes ago
Right, is it low priority or a limitation we're just accepting indefinitely?

Adam Cheney
12 minutes ago
If low priority, then it gets pushed to EOY.

Yong He
12 minutes ago
this particular crash though, I think is a bug we may need to fix.

Yong He
12 minutes ago
I don';t think that crash is related to downstream embedding at all.

Yong He
11 minutes ago
But supporting shared cbuffers fully with downstream embedding, no I don't think that is our current scope.

Yong He
11 minutes ago
slang should never crash, especially in the reflection API and in the front end.

Yong He
10 minutes ago
we can allow it to produce invalid dxil if cbuffer is used cross module.

Adam Cheney
10 minutes ago
It didn't really crash, it just reports an error.

Yong He
10 minutes ago
yeah, there should be no front end errors.

Yong He
10 minutes ago
This is totally valid code.

Yong He
8 minutes ago
In the mid future, we want to ban precompilation of modules that defines any global shader parameters. (edited)

Yong He
7 minutes ago
Like we can have a diagnostic when the user is trying to precompile buffers modules.

Yong He
7 minutes ago
Because bufferrs define a cbuffer that is effecitvely a global shader paraemter.

Yong He
7 minutes ago
That makes buffers ineligible for precompilation.

Yong He
5 minutes ago
An alternative is to allow use of global variables, but all modules linked together must have consistent binding/pipeline layout.

Yong He
5 minutes ago
We don't have to verify that ourselves, and we can leave it to the user.

Yong He
4 minutes ago
But I don't want us to get into this right now, before we have a working spirv path.

Adam Cheney
3 minutes ago
I'll defer it until after the SPIRV path is in place then.

Adam Cheney
2 minutes ago
It seems like it would be fairly easy to avoid precompiling modules that define public global variables.