spirv-std: only enable glam&num-traits's libm features on SPIR-V targets.#1122
spirv-std: only enable glam&num-traits's libm features on SPIR-V targets.#1122fornwall merged 1 commit intoEmbarkStudios:mainfrom LykenSol:libmno
glam&num-traits's libm features on SPIR-V targets.#1122Conversation
|
Accidentally found that this is really broken without Not sure how to control the resolver from EDIT: one very important data point is that this problem is inevitable - you can't really have target-controlled dependencies before |
Draft because I'm not sure if we should do some kind of automated testing for this, I can't think of an obvious way to know "slower floating-point algorithms are being used" (also there's #1115 which may conflict).
Testing-wise the best we can do is probably likely this:
(the above is before this PR, and there are no
libmresults after this PR)