Skip to content
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

Investigate using integer textures with IEEE 754 float encoding. #551

Closed
nsthorat opened this issue Jul 27, 2018 · 2 comments
Closed

Investigate using integer textures with IEEE 754 float encoding. #551

nsthorat opened this issue Jul 27, 2018 · 2 comments
Assignees

Comments

@nsthorat
Copy link
Contributor

nsthorat commented Jul 27, 2018

Recently we disabled integer texture mode (which was using fixed point precision) in favor of half floats on iOS.

However, there are still many devices which do not support the OES_texture_float extension, like Raspberry Pis (see this thread) and Mali T720 GPUs like on Android (see this bug #502).

We could reenable fixed point numbers, but the precision is quite terrible. The other option is to implement IEEE 754 in a shader. We already have a 32 bit float => 4, 8-bit float encoder here, we would just need to write the reverse. Even if performance is poor, it might be better than nothing.

@nkreeger
Copy link
Contributor

Working on introducing half-float changes in the driver for vc4 (driver for Raspberry Pi) - some work tracked here: anholt/mesa#115

@nsthorat
Copy link
Contributor Author

I doubt we're going to do this since it's going to be very slow and we have solutions on most devices, especially with the WASM backend coming soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants