-
Notifications
You must be signed in to change notification settings - Fork 218
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
c[3:4]=0 leads to exception #580
Comments
Exceptions are "regular errors". It's only sticky if you use older hardware. |
To elaborate some more: this is a |
I tried it on a v100 and t4, both post sm_70. In both cases the next command after the exception (e.g. In earlier models, e.g. K80, the exceptions are sticky as you mentioned - I keep getting "illegal instruction" errors no matter how many commands I try. |
Yes, that's the expected behavior. The first is the GPU printing the exception, the second is the CPU detecting an exception happening. Then everything just works again. Do you have any problem with this? |
No I think it is ok, may be worth documenting somewhere if not already.
…On Sun, Nov 29, 2020 at 6:43 PM Tim Besard ***@***.***> wrote:
In both cases the next command after the exception (e.g. println(c)) gets
an exception, but the ones after that start working.
Yes, that's the expected behavior. The first is the GPU printing the
exception, the second is the CPU detecting an exception happening. Then
everything just works again. Do you have any problem with this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#580 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN43JV7CPQOOICWF4XBZFDSSJTZ3ANCNFSM4UFVVDEQ>
.
|
CUDA@2.3.0
Followed with subsequent launch failures for other cuda calls.
The same operation with a regular array just results in a regular error.
The text was updated successfully, but these errors were encountered: