tubs

I don't know if you could signal that more immediately (inline perhaps, without updating the thing on the right)?

To give you some context for the scope of the task: with all the hardware documentation and close to 32 years (combined) experience with that specific architecture it took around two years to write a conformant Vulkan implementation. Not including the compiler, kernel driver, or firmware.

Source: I have worked both on PowerVR and Apple GPU drivers.

i-pace is Jaguar.

That's what I've been doing for non-compliant sites.

> Rust has many benefits and I find it hard to imagine how anyone manages to get any performance-sensitive work done in the cryptocurrency industry with anything else.

b) http://mridgers.github.io/clink/ is bloody fantastic.

Indices are not vertex attributes and thus should not be interleaved with the other data.

    #include <stdlib.h>
    #include <stdio.h>
    #include <sys/types.h>
    #include <sys/mman.h>
    #include <sys/stat.h>
    #include <fcntl.h>
    
    static char c[9];
    
    int p(int i)
    {
        putchar(c[i++]);
        putchar(c[i++]);
        putchar(c[i+(7-i)]);
        putchar(c[i+(8-i)]);
        return 0;
    }
    
    int f(int i, int x) {
        i -= x;
        if(!i) { return p(x); }
        if(i<0) return i+x;
        return x + (f(i,x)  ?: - x);
    }
    
    int d(int a, int b)
    {
        return a-b?d(--a,b)+1:0;
    }
    
    void x(int i)
    {
        if(f(i,3)&f(i,5))printf("%d",i);
        printf("\n");
    }
    
    int i( int c, int target, void (*fn)(int i) )
    {
        return d(target+1,c)?({ fn(c); i(++c,target,fn); }):0;
    }
    
    int main( int argc, char **argv )
    {
        int fd=open(argv[0], O_RDONLY);
        char *m=mmap(NULL,20000,PROT_READ,MAP_PRIVATE,fd,0);
        c[3] = (char)(0x20|m[3]);
        c[4] = m[342];
        c[5] = m[343];
        c[6] = m[351];
        c[8] = c[7] = (char)(((0x38|m[1])<<1)&~0x80);
        i(1,atoi(argv[1]),&x);
        return 0;
    }

fp64, draw_indirect, multi_draw_indirect, shader_buffer_load, bindless_texture.

These are all killer features in writing fast renderers.

http://www.ruf.rice.edu/~mobile/elec518/readings/DevicesAndC...

AMULET was an attempt to make a commercial async chip and it flopped pretty early, one of the reasons being interfacing with anything else in the entire world kinda requires a clock.

http://apt.cs.manchester.ac.uk/projects/processors/amulet/

http://linux.die.net/man/1/xclip