4 ms·
I would not use a work in progress port of Go to compare. This would be better in C to rule out Go runtime issues.
by st3fan 6y ago
I would not use a work in progress port of Go to compare. This would be better in C to rule out Go runtime issues.
- jeffbee 6y agoIt probably is in the Go runtime but I tend to look at things at this level. For example if there's some bug in libc++ that's not something I can overlook when evaluating the M1. There was another comment here that was deleted that accidentally showed the output of running x86-64 go on the M1. That's another weird risk at the user level, that you may unknowingly run the wrong binary through rosetta2 instead of running the native one.