-
-
Notifications
You must be signed in to change notification settings - Fork 450
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
HPX set_difference, set_intersection failure cases #3442
Labels
Milestone
Comments
Here is the code that was attached to the original email:
|
This was referenced Feb 9, 2019
pmikolajczyk41
pushed a commit
to pmikolajczyk41/hpx
that referenced
this issue
Feb 10, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I am an intern on the Visual C++ Libraries Team this summer and have been working on implementing some of their parallel algorithms. While working on implementing the set operations in parallel, I was comparing the performance of my implementation to hpx’s. In doing so, I found some cases in which I got an “Access violation writing location” or “RangeChecks implementation code detected an out of range array access” exception (attempting to run the same executable multiple times resulted in almost always throwing this exception). I don’t believe this is expected behavior, so Billy O’Neal suggested I email you my findings.
The benchmarking program I was using can be found attached. I would comment out one of the algorithms’ calls to test the performance of the other. The specific cases in which I fairly consistently got an exception (in 5-6 tries running the executable, I got the exception every time) were:
set_difference
n=5: all cases
n=50: Cases 1-6, 9
set_intersection:
n=50: Case 9
n=500000: Case 9
n=5000000: Case 9
n=50000000: Case 9
There were some cases where running the executable 5-6 times would finish and allow me to collect data for that case, but I’m afraid I didn’t record those (I was initially just interested in gathering benchmarking results, and it was later suggested that I should notify you of these issues).
Please let me know if you need more information.
Best,
Miya Natsuhara
mailto:t-minat@microsoft.com
The text was updated successfully, but these errors were encountered: