A betterC modular standard library?

[Walter Bright via Digitalmars-d]

On 12/20/2016 5:35 AM, Ilya Yaroshenko wrote:
> On Tuesday, 20 December 2016 at 12:49:53 UTC, Walter Bright wrote:
>
>> I don't see the need to rewrite cpuid because its sole dependency on other
>> object files in Druntime is the static constructor, because the static
>> constructor can be adjusted to not rely on anything else in Druntime.
>>
>> If there are other issues with cpuid, please elucidate.
>
> 1. https://issues.dlang.org/show_bug.cgi?id=16028
> 2. The code is very hard to maintain, fix, extend. This is a reason why
> mir-cpuid was written from scratch without any copy-pasting.
> 3. Library is x86 oriented. Some OSs has interface to fetch unified CPU
> information.
> 4. No TLB information provided.
> 5. Number of CPUs per cache is not know. ARM CPUs may have complex topology
> (plus 3.)

Thank you, but I meant issues that would require it to be separate from 
druntime, not bug fixes or enhancements to account for ever more things being 
added to the CPUID instruction.

BTW, of course it is x86 oriented. Any use of cpuid must be. After all, what 
does "SSSE3.1" mean on ARM?