Google's Lanai Backend Merged Into LLVM
Last month Google engineers posted patches to LLVM for "Lanai", an in-house (apparently network/communications oriented) processor as they were looking to upstream the code. This raised some concerns over Google looking to upstream the code when those outside of the search giant can't even benefit from the code due to the hardware not being public and other concerns, but nevertheless, the code was merged today.
In case you missed the Phoronix coverage last month where we were first to highlight these patches at large, see LLVM Patches Confirm Google Has Its Own In-House Processor. Some were concerned Google was just looking to upstream the code to shift the maintenance burden over to LLVM developers, but Google developers had reaffirmed on the mailing list they look to maintain and continue to improve this code for their in-house benefit.
As of this morning, Lanai was added to LLVM Git/SVN. Thus it's mainlined for the LLVM 3.9 release later this year.
In case you missed the Phoronix coverage last month where we were first to highlight these patches at large, see LLVM Patches Confirm Google Has Its Own In-House Processor. Some were concerned Google was just looking to upstream the code to shift the maintenance burden over to LLVM developers, but Google developers had reaffirmed on the mailing list they look to maintain and continue to improve this code for their in-house benefit.
As of this morning, Lanai was added to LLVM Git/SVN. Thus it's mainlined for the LLVM 3.9 release later this year.
Add A Comment