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

Properly check for self-assignments #2

Closed
karlrupp opened this issue Feb 22, 2013 · 2 comments
Closed

Properly check for self-assignments #2

karlrupp opened this issue Feb 22, 2013 · 2 comments

Comments

@karlrupp
Copy link
Collaborator

Special cases like x = prod(A,x) require additional attention. There are checks in ViennaCL for this case, but they don't provide a unified behavior: Some create a temporary vector (good), others get stuck in asserts() (not so good). Some checks are overly restrictive when ranges are used.

@karlrupp
Copy link
Collaborator Author

Checked the most common operations, a lot of the problems mentioned in the issue have been resolved with the introduction of the scheduler and op_executor. There are still a couple of corner cases left, but these are rather uncommon in practice. This is likely to be resolved with full scheduler integration, hence postponing to 1.6.0.

@karlrupp
Copy link
Collaborator Author

karlrupp commented Nov 7, 2014

Currently no known issues, but a separate regression test desirable. Removing 'bug' label and scheduling for 1.6.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant