Are you referring to the ballpark "specifications" in the article? If so, I don't know of any material that can withstand the stresses of the weights and speeds mentioned in it ... unless you are going for really low wing loading (think dirigible).
Current inflation is mostly supply-side driven. Having said that, M2's biggest jump in its history was in early 2020 (see https://fred.stlouisfed.org/series/M2SL). Its slope before and after is more or less the same. However, I don't think inflation will lag it by more than a year.
> Covid is an autoimmune disease. The Over active immune response is what is killing people.
The virus triggers an acute immune response. This is not the same as an autoimmune disease, it may be the opposite. Also, people with certain blood types that have better clotting ability seem to be at a disadvantage.
> But on 64-bit windows the default exception handling (SEH) uses a similar mechanism than Linux and should have comparable performance.
AFAIK SEH in Windows calls RaiseException() which in turn causes a user/kernel mode transition, probes for exception/termination handlers, and vectored exception handlers depending on the severity. It's been a while but I'm not sure the code GCC generates in Linux is quite like this.
> benchmarks have shown that exceptions are generally faster
The blog post you linked to says "Immediately we see that once the stack depth grows above a certain size (here 200/3 = 66), exceptions are always faster. This is not very interesting, because call stacks are usually not this deep (enterprise Java notwithstanding). For lower depths there is a lot of noise, especially for GCC ..." So ... not exactly "generally faster".
Also, the test is only for Linux. The same test on Windows/VC++ will probably run a lot slower ... again not "generally faster"
I was referring to the RTL-based IP that goes into each subsystem of the CPU, hence the analogy to code. You're talking about compiler instruction scheduling, a lot of which are a bunch of non-AI algorithms. If I'm missing something, I would appreciate the references to the functionality you're referring to.
IIRC, the data structure that they used was not thread-safe. There eventually had to be an interlocked compare exchange operation which slowed throughput. Also, I couldn't imagine this working correctly in out-of-order cores without memory barriers at the very least.