I think having a single specialization is nearly impossible in a real-world application for a structure like a matrix so I am not really sure of the value.
It's kind of strange that they even call that a specialization - my (limited) understanding of specializations is when you write custom implementations for certain parameters types (the classic sort() uses counting sort for small domains (char keys), and quick-sort for others (arbitrary keys)).
-----Original Message-----
From: ⚛ <0xe2.0x9a.0...@gmail.com>
Sent: Mar 3, 2020 4:35 PM
To: golang-nuts
Subject: Re: [go-nuts] Go without garbage collector--On Tuesday, March 3, 2020 at 11:25:22 PM UTC+1, Robert Engels wrote:
A key statement in the link “ The JIT-generated code is significantly faster than the ahead-of-time-generated code for small matrix sizes.”
Which is what you were arguing was not possible... you can’t have it both ways.There is another piece of information that can be found there: runtime performance of Single Specialization is approximately the same as runtime performance of the JIT-ed code.
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/dd32ec49-3d7c-4984-b57b-510746da8f55%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/1157025190.3326.1583275964599%40wamui-pluto.atl.sa.earthlink.net.