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

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): my results for Intel Core i7-6700K CPU @ 4.00GHz rev.2 (the one with sgx) https://gist.github.com/Zoadian/f53d818e714a849ba7f34bbec2f3339a awesome!

Re: new cpuid is ready for comments

Output cpuid for Intel(R) Core(TM) i5-3320M CPU @ 2.6 GHz: https://gist.github.com/redstar/a1c9c85f17f2c24834050b5b0b734d3d

Re: new cpuid is ready for comments

On Tuesday, 12 July 2016 at 15:24:29 UTC, Guillaume Chatelet wrote: On Tuesday, 12 July 2016 at 13:23:46 UTC, Ilya Yaroshenko wrote: On Tuesday, 12 July 2016 at 12:46:26 UTC, Guillaume Chatelet wrote: On Monday, 11 July 2016 at 16:30:44 UTC, Ilya Yaroshenko wrote: Hello :-) `cpuid` package

Re: new cpuid is ready for comments

On Mon, Jul 11, 2016 at 04:30:44PM +, Ilya Yaroshenko via Digitalmars-d-announce wrote: [...] > 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. [...] AMD Phenom(tm) II X6 1055T Processor

Re: new cpuid is ready for comments

On Friday, 15 July 2016 at 15:05:53 UTC, Ilya Yaroshenko wrote: On Friday, 15 July 2016 at 12:10:22 UTC, Claude wrote: [...] Yes! Finally we need the final code for LDC, it support ARM assembler. http://wiki.dlang.org/LDC_inline_assembly_expressions [...] No, I have not. Thank you for

Re: new cpuid is ready for comments

On Friday, 15 July 2016 at 12:10:22 UTC, Claude wrote: On Monday, 11 July 2016 at 16:30:44 UTC, Ilya Yaroshenko wrote: [...] What exactly do you need for ARM architecture? I have an ARM target and I have tried to run a library[1] to get some CPU info. I hacked in the source files to just

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): Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz https://gist.github.com/jmh530/2f1694711085176e007461ae8218a759 Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz

Re: new cpuid is ready for comments

On Monday, 11 July 2016 at 16:30:44 UTC, Ilya Yaroshenko wrote: ARM contributors are wanted! What exactly do you need for ARM architecture? I have an ARM target and I have tried to run a library[1] to get some CPU info. I hacked in the source files to just build and link the CPU info code.

Re: new cpuid is ready for comments

AMD FX 8350 test https://gist.github.com/burjui/a661499a2daa93302395d136b6c99152 cpuinfo https://gist.github.com/burjui/8c10924284c1c1f9cce33bcd2b71d863

Re: new cpuid is ready for comments

Intel Core i5: https://gist.github.com/claudemr/aa99d03360dccc65d7967651011dc8ca

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:

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:

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

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)

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

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

Re: new cpuid is ready for comments

On Tuesday, 12 July 2016 at 15:24:29 UTC, Guillaume Chatelet wrote: On Tuesday, 12 July 2016 at 13:23:46 UTC, Ilya Yaroshenko wrote: On Tuesday, 12 July 2016 at 12:46:26 UTC, Guillaume Chatelet wrote: On Monday, 11 July 2016 at 16:30:44 UTC, Ilya Yaroshenko wrote: Hello :-) `cpuid` package

Re: new cpuid is ready for comments

On Tuesday, 12 July 2016 at 15:24:29 UTC, Guillaume Chatelet wrote: 2. As far as I know, Android does not expose either CPU identification or cache structure information to userspace. Please do correct me if I'm wrong and this library found a way around that --- but from a cursory look at the

Re: new cpuid is ready for comments

On Tuesday, 12 July 2016 at 13:23:46 UTC, Ilya Yaroshenko wrote: On Tuesday, 12 July 2016 at 12:46:26 UTC, Guillaume Chatelet wrote: 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

Re: new cpuid is ready for comments

On Tuesday, 12 July 2016 at 12:46:26 UTC, Guillaume Chatelet wrote: 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. Hey Ilya, Quick question: where do the data come from/how

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. Hey Ilya, Quick question: where do the data come from/how reliable do you think they are?

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

new cpuid is ready for comments

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