-
Notifications
You must be signed in to change notification settings - Fork 486
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
[LoweringContext] SPMD support #8418
Conversation
8e035c9
to
a313cee
Compare
@JackCaoG @tengyifei, do we have a plan for different IR values that we can not deduce from the input alone? Referencing Jack's example:
I could look into creating a minimal framework that traces to identify the ancestor node that has sharding specs, if there are no clashes, nor ops that does not allow us to. Do we have any other suggestions for this one, or if something already exists? Worst case scenario, we enforce the inputs with sharding specs as an invariant. |
FYI, if we do not eagerly instantiate the tensors on the CPU, but forward it to the device data with rng:
It just seems that the HLO text from the computation does not show the sharding but if using |
3fae03a
to
476602d
Compare
f79218f
to
449a6ee
Compare
Added more coverage with IR dump graphs + test cleanup commit to avoid lingering files in case of failures. |
939d298
to
05c996e
Compare
I'll take a look |
0f128c5
to
00c0e96
Compare
Various conflicts, synced and moved to #8471. |
In this PR, we extend the lowering context to support SPMD.
Testing