Live data from Hacker News

Lanai, the mystery CPU architecture in LLVM

q3k.org

51–60 of 163 posts

Re: Lanai, the mystery CPU architecture in LLVM

#51

Earlier quoted context omitted.

> The CEO capped the full time headcount at 49 people so he wouldn’t be subject to California law requiring him to provide his employees with a health plan. Can you imagine being this stingy and short sighted? The employees are largely PhDs and he is willing to cripple his company to avoid paying benefits.

I'm not sure that part of Scott's article was accurate. I worked remotely, and I'm pretty sure that I was offered benefits. I declined them, and used my wife's benefits because they were less expensive, and meshed better with local health care providers. EDIT: And I know we had a 401K

I worked there and have evidence that this statement in the blog is not true, and I'm being down-voted?

Re: Lanai, the mystery CPU architecture in LLVM

#52

Earlier quoted context omitted.

I'm not sure that part of Scott's article was accurate. I worked remotely, and I'm pretty sure that I was offered benefits. I declined them, and used my wife's benefits because they were less expensive, and meshed better with local health care providers. EDIT: And I know we had a 401K

I worked there and have evidence that this statement in the blog is not true, and I'm being down-voted?

I don't think so, your comment is black text for me, so it's either at it's original score or higher.

Re: Lanai, the mystery CPU architecture in LLVM

#53

Earlier quoted context omitted.

> The CEO capped the full time headcount at 49 people so he wouldn’t be subject to California law requiring him to provide his employees with a health plan. Can you imagine being this stingy and short sighted? The employees are largely PhDs and he is willing to cripple his company to avoid paying benefits.

It’s not even that hard or expensive to offer 401k, health, life insurance in a startup. Been there, done that.

At least 10k/yr/employee.

Re: Lanai, the mystery CPU architecture in LLVM

#55

I gotta say, if I was the BDFL of llvm, I would kick this out of tree without a second thought. Why on earth should a foss project support a private architecture? How many man-hours have been wasted waiting for the Lanai backend to compile? Not to mention applying project-wide refactoring to the Lanai code.

Removing architectures because they’re obsolete/maintainers can’t be found, I can see (and the llvm maintainers agree. They removed Alpha at some time, for example), but because they’re proprietary? That would mean kicking out x86, x64, ARM, AMD Terascale, IBM’s z/architecture, etc.

I’m sure clang would be very happy with that.

Re: Lanai, the mystery CPU architecture in LLVM

#56
post #4

I 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...

This line in that post is mystifying: they peddled Infiniband, an inferior design based on bus technology, but repositioned as a point to point network

At least initially (~2005 or so?) we had customers who were given free IB for their HPC clusters ripping the IB out and replacing it with with paid Myrinet installations because they could never get their IB clusters to work reliably.

Although we had the superior product, we could not market our way out of a wet paper bag. Our CEO counted on our (then) superior engineering & expected our products to market themselves. Eventually the IB engineering caught up and surpassed ours, but our marketing never even came close to theirs, so they were the clear winner.

Re: Lanai, the mystery CPU architecture in LLVM

#57
post #43

Earlier quoted context omitted.

This line in that post is mystifying: they peddled Infiniband, an inferior design based on bus technology, but repositioned as a point to point network

I think that's a confusing reference to the fact that InfiniBand initially was supposed to be also a replacement for system-internal buses (i.e. a PCI replacement), before PCIe took that place instead.

Yeah that makes sense, it's an RDMA protocol, and PCIe has wayyyy more in common with infiniband then it does with legacy PCI.

Re: Lanai, the mystery CPU architecture in LLVM

#58
post #31
post #14

Earlier quoted context omitted.

Would something like this be accepted in open source projects that are not significantly driven by Google? E.g. would Linux accept code for drivers / architectures that are not available to the public? I'm genuinely curious.

Given how ridiculously strict the Linux folks are being with the DXGKRNL stuff that MS is working on (which is public as part of WSLg), I would say definitely not.

I think that has more to do with DXGKRNL coming from Microsoft than any policy that would be applied to other contributers.

Re: Lanai, the mystery CPU architecture in LLVM

#59
post #12

Earlier quoted context omitted.

Why can you not comment? Certainly any NDA you signed must be expired by now. 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 anyt…

Hard to make a more wrong post (everything apart from the advice to consult a lawyer is incorrect).

I see that you have not followed the bit you approved of.

Re: Lanai, the mystery CPU architecture in LLVM

#60
post #4

I 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...

> The CEO capped the full time headcount at 49 people so he wouldn’t be subject to California law requiring him to provide his employees with a health plan. Can you imagine being this stingy and short sighted? The employees are largely PhDs and he is willing to cripple his company to avoid paying benefits.

I believe that There are many things that kick in at 50 people. It's oversimplifying to assume this was due to not wanting to offer benefits.

First google hit: https://www.aeisadvisors.com/california-compliance-is-my-com...

Post reply on HN