Earlier quoted context omitted.
The fact that they developed and upstreamed an LLVM backend indicates that they probably did something with it.
The Google way: Force the rest of the world adjust to your new "cool thing", and then kill it because it wasn't that great.
Lanai, the mystery CPU architecture in LLVM
11–20 of 163 posts
Re: Lanai, the mystery CPU architecture in LLVM
#12I worked for Myricom 2001->2013, and Google 2013->2015. And, wow, I wish I could comment on this thread.. :) EDIT: Scott's Medium blog post linked from this article is fascinating: https://medium.com/swlh/myricom-an-hpc-story-and-lessons-lea...
PSA: If you are not getting continuing payments, any contracts you signed are void. Technically, I gather you are supposed to notify the other party that you are terminating your participation in the contract. Even if you are getting ongoing payments, you can opt out of that, too.
(This is not legal advice. Consult an actual lawyer for anything that matters.)
Re: Lanai, the mystery CPU architecture in LLVM
#13Re: Lanai, the mystery CPU architecture in LLVM
#14Earlier quoted context omitted.
The Google way: Force the rest of the world adjust to your new "cool thing", and then kill it because it wasn't that great.
Google isn't really forcing anyone to do anything in this case. Another RISC backend that was made clear would be ripped out of upstream the instant the Google maintainers stopped responding isn't really an imposition.
E.g. would Linux accept code for drivers / architectures that are not available to the public? I'm genuinely curious.
Re: Lanai, the mystery CPU architecture in LLVM
#15Earlier quoted context omitted.
The Google way: Force the rest of the world adjust to your new "cool thing", and then kill it because it wasn't that great.
Google isn't really forcing anyone to do anything in this case. Another RISC backend that was made clear would be ripped out of upstream the instant the Google maintainers stopped responding isn't really an imposition.
Seems the maintainers were more than happy to accept it, and even had policies in place for such contributions. One maintainer even mentioned it's a good policy because it brings more developers into using LLVM's ToT, which is overall good for project health.
Re: Lanai, the mystery CPU architecture in LLVM
#16Re: Lanai, the mystery CPU architecture in LLVM
#17I worked for Myricom 2001->2013, and Google 2013->2015. And, wow, I wish I could comment on this thread.. :) EDIT: Scott's Medium blog post linked from this article is fascinating: https://medium.com/swlh/myricom-an-hpc-story-and-lessons-lea...
I just want to know why it needs to be in-tree.
Re: Lanai, the mystery CPU architecture in LLVM
#18I don't get this. Searching for [lanai cpu] shows tons of links on the LANai cpu architecture from Myricom, purchased by Google.
Re: Lanai, the mystery CPU architecture in LLVM
#19https://github.com/chriseth/notes/blob/186d7ea0742336ed38e39...
"TrueBit - Off-Chain Computations for Smart Contracts"
Re: Lanai, the mystery CPU architecture in LLVM
#20I worked for Myricom 2001->2013, and Google 2013->2015. And, wow, I wish I could comment on this thread.. :) EDIT: Scott's Medium blog post linked from this article is fascinating: https://medium.com/swlh/myricom-an-hpc-story-and-lessons-lea...
Yeah, that blog post was a great reference to get a general overview of What Happened At Myricom. ... and I just hope I didn't write anything factually wrong in TFA. :)