-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Advent 2019: Tour of Go Compilers #350
base: master
Are you sure you want to change the base?
Conversation
Thanks Mohammed for the time and effort you've put into this article. It's very informative, I didn't know there were as many Go compilers! I suggest a final run of proofreading to fix some
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Mohammed,
Thanks for this write-up on the various implementations of Go compilers. It was a joy to read (and review)!
I only found a few typos, other than that, a spectacular write-up :)
Wish you a happy winter holidays.
Cheerful regards,
Robin
Thank you @AliAlhajji and @mewmew for your review and kind words! |
@bketelsen, this is supposed to be published today. Anything missing? |
I'd also love to see this post published, as it's very insightful and gives a good introduction to the Go compiler landscape. |
Co-Authored-By: Robin Eklind <[email protected]>
I have collected benchmark data for gc, gccgo (-O2 and -O3), and gollvm but opted not to include them because tables aren't neat and images of charts don't show enough details of thee variations.