4 ms·

I understand why ATLAS would need to do something like this maybe up until 10 years ago. I also understand the time and performance hard constraints the library

I understand why ATLAS would need to do something like this maybe up until 10 years ago. I also understand the time and performance hard constraints the library needs to provide applications with, specially in some scientific experiments. However, this type of static linking is very weird in today's architectures, specially when considering that an application can run anywhere, from a light bulb to a top notch server hosted in the cloud and elsewhere. It specially bugs me to think that people leading some of these projects are so stubborn to the point of not accepting the new reality imposed by today's software and system architectures.

sharikone 5y ago
I agree that refusing to compile is stubborn on their part. But tailoring the build to your system is very valuable, at least as an option. And a big part of the blame lies with the CPU and OS manufacturers that fail to provide good consistent performance measurement options that traverse all the endless layers of abstraction that extend from the transistors to a user space program nowadays
- genewitch 5y ago
  On the face it seems like CPU manufacturers should be able to put actual performance numbers out; until we realize that the temperature characteristics - and therefore performance - are non-deterministic. This fact allows hardware RNG from thermal emissions on consumer grade CPUs to output at least 3 megabits of 'entropy' per second. The same as 3,000,000 coin flips. I may be misunderstanding what is going on, though.