| #define BINKGL_LIST \ | |
| /* ret, name, params */ \ | |
| GLE(void, LinkProgram, GLuint program) \ | |
| GLE(void, GetProgramiv, GLuint program, GLenum pname, GLint *params) \ | |
| GLE(GLuint, CreateShader, GLenum type) \ | |
| GLE(void, ShaderSource, GLuint shader, GLsizei count, const GLchar* const *string, const GLint *length) \ | |
| GLE(void, CompileShader, GLuint shader) \ | |
| GLE(void, GetShaderiv, GLuint shader, GLenum pname, GLint *params) \ | |
| GLE(void, GetShaderInfoLog, GLuint shader, GLsizei bufSize, GLsizei *length, GLchar *infoLog) \ | |
| GLE(void, DeleteShader, GLuint shader) \ |
| // values in nanoseconds | |
| static U64 timer() | |
| { | |
| struct timespec ts; | |
| if (clock_gettime(CLOCK_MONOTONIC, &ts) != 0) | |
| return 0; | |
| return (U64)ts.tv_sec * 1000000000 + (U64)ts.tv_nsec; | |
| } |
| Why do compilers even bother with exploiting undefinedness signed overflow? And what are those | |
| mysterious cases where it helps? | |
| A lot of people (myself included) are against transforms that aggressively exploit undefined behavior, but | |
| I think it's useful to know what compiler writers are accomplishing by this. | |
| TL;DR: C doesn't work very well if int!=register width, but (for backwards compat) int is 32-bit on all | |
| major 64-bit targets, and this causes quite hairy problems for code generation and optimization in some | |
| fairly common cases. The signed overflow UB exploitation is an attempt to work around this. |
Prototype "slightly higher level" abstraction layer over modern graphics API:s Written mostly in 20 minute chunks while commuting (expect quality thereafter ;)
Still a lot of blemishes and missing features:
Orthodox C++ (sometimes referred as C+) is minimal subset of C++ that improves C, but avoids all unnecessary things from so called Modern C++. It's exactly opposite of what Modern C++ suppose to be.