Re: new cpuid is ready for comments
On Monday, 11 July 2016 at 16:30:44 UTC, Ilya Yaroshenko wrote: Please report your CPU (GitHub/Gist): Late 2015 MacBook Pro Intel i5 https://gist.github.com/JackStouffer/6870bde82788ae039afe0aaf0d7bf4ba
Re: new cpuid is ready for comments
Am Mon, 11 Jul 2016 16:30:44 + schrieb Ilya Yaroshenko: > Please report your CPU (GitHub/Gist): Instead of yet another Haswell/Broadwell, here is an oldie but goldie: A 16 year old Pentium-III-M from an IBM T23 notebook: https://gist.github.com/mleise/4ed5637371ca5cea07bef8241adc7d80 I repost this in your bug tracker momentarily. -- Marco
Re: Vision document for H2 2016
On Thursday, 7 July 2016 at 19:55:51 UTC, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei Folks, One of the main obstacles I see to the adoption of a language is its ecosystem. Perhaps the vision should include a structure of frameworks we would like to see being developed, with a community process similar to what we follow for the language. vibe.d is already a tremendous asset, but we are lacking the equivalent of DBI, slf4j, JMS, etc. Does this sound like a good idea, and if so, does anybody want to help put something together like that? j.
Re: new cpuid is ready for comments
On Thursday, 14 July 2016 at 13:04:56 UTC, Kirill Babikhin wrote: Intel(R) Core(TM)2 CPU 4400 @ 2.00GHz https://gist.github.com/qsimpleq/78ed456a289f9cc418f69527298e3e9a#file-intel-r-core-tm-2-cpu-4400-2-00ghz
Re: new cpuid is ready for comments
On Monday, 11 July 2016 at 16:30:44 UTC, Ilya Yaroshenko wrote: Please report your CPU (GitHub/Gist): AMD Phenom(tm) 9550 Quad-Core Processor https://gist.github.com/qsimpleq/78ed456a289f9cc418f69527298e3e9a
Re: new cpuid is ready for comments
On Thursday, 14 July 2016 at 12:00:12 UTC, Brad Jones wrote: Very nicely done. Following Guillaume, I too have added the output of `cat /proc/cpuinfo`. Here's my contribution. cpuid for Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz on Intel NUC: https://gist.github.com/britishempire/dad6f7d0e24dff096d7ef35e62520387 In the off chance a 404 is thrown: https://gist.github.com/brdjns/dad6f7d0e24dff096d7ef35e62520387
Re: new cpuid is ready for comments
On Monday, 11 July 2016 at 16:30:44 UTC, Ilya Yaroshenko wrote: Hello :-) `cpuid` package is core.cpuid analog. It would be used by future D BLAS implementation. Why it is better? See https://github.com/libmir/cpuid#api-features https://github.com/libmir/cpuid#implementation-features https://issues.dlang.org/show_bug.cgi?id=16028 Please report your CPU (GitHub/Gist): ``` dub fetch cpuid dub test cpuid ``` ... AMD was not tested at all and I hope to see your reports. ARM contributors are wanted! Destroy! Best regards, Ilya Docs: http://docs.cpuid.dlang.io GitHub: https://github.com/libmir/cpuid Dub: cpuid Very nicely done. Following Guillaume, I too have added the output of `cat /proc/cpuinfo`. Here's my contribution. cpuid for Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz on Intel NUC: https://gist.github.com/britishempire/dad6f7d0e24dff096d7ef35e62520387
Re: new cpuid is ready for comments
Intel(R) Xeon(R) CPU X5690 @ 3.47GHz https://gist.github.com/drug007/738f7ce8ba73f4413d11e170ab36c7e3 output for cpuid for VM (VirtualBox) running on Intel(R) Xeon(R) CPU X5690 @ 3.47GHz https://gist.github.com/drug007/76750ba962e84be494b8bf11bd84a3a7 output cpuid for Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz https://gist.github.com/drug007/3f7f0701b3d4f1f40c422acc36e343d7
Re: new cpuid is ready for comments
On Monday, 11 July 2016 at 16:30:44 UTC, Ilya Yaroshenko wrote: Please report your CPU (GitHub/Gist) Running on Mac Pro Intel Xeon Quad-Core x2 https://gist.github.com/Dechcaudron/e6eeb17972316785d7c07c409a2ed092