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.

Sign up for GitHub

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

Jump to bottom

ukt necessity #10

Open
anders34 opened this issue May 29, 2016 · 3 comments
Open

ukt necessity #10

anders34 opened this issue May 29, 2016 · 3 comments
Labels
Answered

Comments

@anders34
Copy link

anders34 commented May 29, 2016 •
edited
Loading

I'm a little confused about in heat.c, why we have ukt. If we already have uk, why do we need a duplicate of it at ukt.
@anders34
Copy link
Author

Because uk is a private variable to each thread/process, right? So we shouldn't need to make ukt...

@swcarmer
Copy link

I agree, we could use the uk pointer passed in as our ukt, which negates the need for the array copies as well.

@anders34 anders34 changed the title ukt and temp ukt necessity May 30, 2016
@quantheory
Copy link
Member

It's true that ukt is unnecessary in this case. If there were two separate "input" and "output" pointers, and you weren't allowed to change the "input" array, then it would be necessary to make a copy. But in this case, it's admittedly an extra step.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Answered
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@quantheory @anders34 @swcarmer