We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
idcpu
I think it would be efficient if we had a function that is make64bit(cpu, id) that we can assign straight to the idcpu array value:
make64bit(cpu, id)
pa_idcpu[ip] = newFunction(cpuid, pid+ip);
Do we have such a thing already?
I work around this now via
pa_idcpu[ip] = 0; amrex::ParticleIDWrapper{pa_idcpu[ip]} = pid+ip; amrex::ParticleCPUWrapper{pa_idcpu[ip]} = cpuid;
to avoid valgrind (uninit data read) warnings during the first assign.
x-ref: ECP-WarpX/WarpX#4653
The text was updated successfully, but these errors were encountered:
Add helper function for setting id and cpu simultaneously. (#3733)
09fc44a
Also sneaking in a small ignore_unused fix. Close #3731. Co-authored-by: Axel Huebl <[email protected]>
atmyers
Successfully merging a pull request may close this issue.
I think it would be efficient if we had a function that is
make64bit(cpu, id)
that we can assign straight to theidcpu
array value:Do we have such a thing already?
I work around this now via
pa_idcpu[ip] = 0; amrex::ParticleIDWrapper{pa_idcpu[ip]} = pid+ip; amrex::ParticleCPUWrapper{pa_idcpu[ip]} = cpuid;
to avoid valgrind (uninit data read) warnings during the first assign.
x-ref: ECP-WarpX/WarpX#4653
The text was updated successfully, but these errors were encountered: