In the UK a CIC (Community Interest Company) is an option, which can legally oblige the company to act in the interest of "the community they serve". I think in the USA a benefit corporation might be similar.
Alternatively if Komoot was a worker co-op a sell-out would only be possible with consent from the employees. Consumer co-ops (where users can vote too) are also an option but with more caveats.
I'm using RocM OpenCL right now, which I believe is the approved option, or will be. Personally I've not had any issues with it - I can certainly use Blender with it, although the performance right now is so-so (I only have a cheap APU though, so hardly surprising).
I don't believe I have any blobs, other than the firmware one, which is true regardless - can you tell me what blobs you mean?
I'm not saying "hey this is definitely due to climate change", but ridiculing the suggestion that an event apparently linked to increased ocean temperatures might have something to do with climate change seems a little off.
Most DSPs I've worked with have an assortment of really specific extra instructions added for the particular application. I suspect these DSPs are similar - adding a new codec probably means adding a few more instructions, or even the odd hardware block dangling off the side.
I'm not really qualified to answer this, but I suspect the instruction decoder(s?) would be decoupled from register state as much as possible (unless x86 is even weirder than I thought).
Given this, I suspect wiring in a path all the way from the relevant versions of the relevant registers might be quite expensive. Plus part of the decode logic now needs to block on a register value - so a timing based attack might find these.
This sounds like a good way to learn, but I would worry about picking up bad habits. Do you have any recommendations of (C) projects etc. that are particularly well written?
I had an interesting time writing a JIT for Piet some time ago. Piet is a pretty weird language in a few non-obvious ways. From what I remember:
* Execution moves between blocks of colour. Flood fill algorithms are a valid compiler optimisation!
* Execution can move left/right/up/down. You can't necessarily tell what will be executed without doing it. The 'codel chooser' stuff means you can exit a colour block in two different ways depending on program state (plus left/right/up/down, so 8 ways total...).
* Instructions are encoded in the difference between colour blocks.
* Piet is otherwise a fairly straightforward stack machine.
I've been wanting to do something like this for a while. I'd quite like something that collects commentary about the state of countries around the word, but I'm lacking decent sources, especially for outside of the west. Have you found any particularly enlightening sources of such things you'd care to share?
Alternatively if Komoot was a worker co-op a sell-out would only be possible with consent from the employees. Consumer co-ops (where users can vote too) are also an option but with more caveats.