Actions: openxla/shardy
Actions
283 workflow runs
283 workflow runs
MeshAttr
in a TensorShardingAttr
instead of referencing a symbol MeshOp
by name.
Buildifier
#285:
Pull request #120
opened
by
copybara-service
bot
sdy::NamedComputationOp
in/out shardings and make it adhere to ShardableDataFlowOpInterface
, and add op result data flow op interface methods.
Buildifier
#284:
Pull request #119
opened
by
copybara-service
bot
CallOp
s with backend_configs
to NamedComputationOp
s.
Buildifier
#281:
Pull request #116
opened
by
copybara-service
bot
ManualAxesCleanupPass
to pipeline
Buildifier
#278:
Pull request #114
opened
by
copybara-service
bot
sdy::NamedComputationOp
.
Buildifier
#275:
Pull request #111
synchronize
by
copybara-service
bot
sdy::NamedComputationOp
.
Buildifier
#272:
Pull request #111
opened
by
copybara-service
bot
ManualComputationOp
of enforcing manual axes to be sorted and used by all in/out shardings.
Buildifier
#271:
Pull request #109
synchronize
by
copybara-service
bot
addPointwiseIfDimSizesMatch
.
Buildifier
#269:
Pull request #110
synchronize
by
copybara-service
bot
addPointwiseIfDimSizesMatch
.
Buildifier
#268:
Pull request #110
synchronize
by
copybara-service
bot
addPointwiseIfDimSizesMatch
.
Buildifier
#267:
Pull request #110
opened
by
copybara-service
bot
ManualComputationOp
of enforcing manual axes to be sorted and used by all in/out shardings.
Buildifier
#266:
Pull request #109
opened
by
copybara-service
bot
-sdy-apply-sharding-constrains
where we replaces uses of an input with a chain of ShardingConstraintOp
s without handling the case where the use is located before the chain.
Buildifier
#265:
Pull request #108
synchronize
by
copybara-service
bot
-sdy-apply-sharding-constrains
where we replaces uses of an input with a chain of ShardingConstraintOp
s without handling the case where the use is located before the chain.
Buildifier
#264:
Pull request #108
opened
by
copybara-service
bot
ShardingConstraintOp
s, with no branched uses, with the result of that chain. Which effectively gives those uses the sharding of the last constraint in the chain rather than the first.
Buildifier
#263:
Pull request #106
synchronize
by
copybara-service
bot
ShardingConstraintOp
s, with no branched uses, with the result of that chain. Which effectively gives those uses the sharding of the last constraint in the chain rather than the first.
Buildifier
#262:
Pull request #106
synchronize
by
copybara-service
bot