A popular post on r/wallstreetbets[1] summarizes Michael Burry’s thesis that CPI (consumer price index) is unaffected as long as inflation isn’t directly impacting consumers of the bag of goods that make up CPI. When there are fewer jobs, these consumers aren’t able to influence the prices of these goods (because they aren’t being paid inflated wages), and the metric commonly used to evaluate inflation is unchanged.
I would guess the processor would just cause an exception/interrupt and it would just call an OS level exception/interrupt handler which would probably tell the user what the exception/interrupt was that occured; in this case an unsupported instruction.
I've found the M1's 128bit instructions to be quite fast. My M1 MacBook Air can hit 90GFlops on a single core. My 2019 16" MacBook Pro is only 1.5 times faster at 135GFlops per core, despite double the vector width.
Are people using named tensors a lot these days? I haven't seen a lot of code using them but I also haven't been looking at a lot of tensor code lately.
I'm not sure. My interest is in "Python first" approach, after all, the whole idea of developing a small Python implementation (first MicroPython, then Pycopy) was to write code in Python, not C/C++. Where interfacing with existing libraries is required, the best way to do that is again from Python side, using FFI (https://pycopy.readthedocs.io/en/latest/library/ffi.html). That however usually means code written in C, as C has a simple and stable enough ABI to which it's easy to interface.
In other words, things like interfacing with C++ is somewhat outside of Pycopy scope. But they very well may be in the scope of MicroPython project (and if they're available for MicroPython, they should be also usable for Pycopy, as 2 projects are largely compatible.)
