You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello! the document at http://docs.gl/el3/smoothstep says Results are undefined if edge0 ≥ edge1. i have been working with shaders in max/msp/jitter in GLSL #version 330 and find that if `edge0 > edge1', the result is not undefined, rather the behavior is simply inverted. i am not sure whether this is an error in your documentation or just an eccentricity/enhancement of cycling 74's implementation, but i figured i would report in nonetheless!
The text was updated successfully, but these errors were encountered:
Undefined behaviour means that it might work on a certain platform, it might not, vendors are free to implement UB however they want. If it works correctly on your machine, that's great, but you can't rely on it being correct on other hardware, because basically anything could happen.
On Fri, Jun 12, 2020 at 3:34 PM Botondar ***@***.***> wrote:
Undefined behaviour means that it might work on a certain platform, it
might not, vendors are free to implement UB however they want. If it works
correctly on your machine, that's great, but you can't rely on it being
correct on other hardware, because basically anything could happen.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#85 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKWDUIF3WPBXLXF2RNVXZ33RWKUOBANCNFSM4NYXP3PQ>
.
hello! the document at http://docs.gl/el3/smoothstep says
Results are undefined if edge0 ≥ edge1.
i have been working with shaders in max/msp/jitter in GLSL#version 330
and find that if `edge0 > edge1', the result is not undefined, rather the behavior is simply inverted. i am not sure whether this is an error in your documentation or just an eccentricity/enhancement of cycling 74's implementation, but i figured i would report in nonetheless!The text was updated successfully, but these errors were encountered: