Skip to content
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

exatn::sync(TensorOperation) is inconsistent #34

Open
DmitryLyakh opened this issue May 12, 2020 · 0 comments
Open

exatn::sync(TensorOperation) is inconsistent #34

DmitryLyakh opened this issue May 12, 2020 · 0 comments
Assignees
Labels
invalid This doesn't seem right

Comments

@DmitryLyakh
Copy link
Member

exatn::sync executed on exatn::TensorOperation uses its Id assigned during the operation submission. This Id refers to a local DAG node. Two potential problems: (1) Attempt to sync a tensor operation that has never been submitted will result in a SegFault since the Id is not set yet; (2) The global exatn::sync is expected to destroy the current DAG, so a later attempt to access its node will result in a SegFault. A proper way to sync a tensor operation is to sync every output operand.

@DmitryLyakh DmitryLyakh added the invalid This doesn't seem right label May 12, 2020
@DmitryLyakh DmitryLyakh self-assigned this May 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

1 participant