1,021 karma · joined September 21, 2010
That's been true of lookup tables for a long while now.
You have control if you are running your own services on top of the main cloud providers, but if it is in O365 or GMail/GApps it used to be a different story, and this precluded their use by a bunch of .au organisations (universities, Govt departments) early on.
So now some of these orgs that need to have data stored in .au for privacy reasons (among other reasons) are subject to these new badly formed laws in some kind of twisted catch-22.
The market they are headed for is embedded, where every cent of the BOM counts. Licensing costs can add up surprisingly fast as part of that.
Server parts are a big step above that - MIPS used to play there, but after a short peak they failed many times over. It tried in the networking and embedded space for a while, but then had its lunch stolen by all the cheap ARM vendors from below, and stomped on by x86 from above.
And then desktop/laptop parts? Unless you are Apple (and even then), pushing a new arch on the desktop is a massive, expensive task, and I can’t see it being worthwhile.
Trying -march=haswell might give closer results.
On the other hand, if using an older gcc and it can’t identify your processor, march=native will result in mtune=generic and much head scratching with results.
The decompression just takes a while.
I had a TileGX dev board and ported our product at the time (nearly 10 years ago). It was an ok arch but that’s a tough niche to fight for.
Strata title laws have been changed recently, but the system is slow to catch up to these cowboys.
Instructions get decoded and some end up looking like RISC instructions, but there is so much macro- and micro-op fusion going on, as well as reordering, etc, that it is nothing like a RISC machine.
(The whole argument is kind of pointless anyway.)
I’ve spent a lot of time making cross-compile work for complicated builds. It can be tedious and frustrating fighting compilers and build systems to get it right.
Sometimes it is necessary because the target didn’t have a complete native toolchain, but other times because the target was just so incredibly slow for large builds.
I haven’t built anything with them, but these Arm servers appear to be neither of those two cases.
The China regions might not have all the AWS services present, and they have some extra restrictions, but they aren’t some kind of clones of AWS software.
Unless I’m missing something, they are the same versions of what runs in the other regions.
This is less fragile and requires less dependence on replacing make in the $PATH.
That is the case with GCCs __builtin functions. With a few exceptions, intrinsics are basically macros for inline asm that the compiler can reason about.
If on x86-64 you use a _mm256* intrinsic and compile without AVX support you just get a compile error, not a pair of equivalent SSE instructions.
Works fine for me.
Which is important context for many of her posts in the last month or so.
Obviously there is an additional mystery world of option grants at Amazon that we aren’t aware of.
1. Atlassian 2. Canva? 3. ??
I can’t think of anything else big and “impressive”. Who am I forgetting?
The last cheque I wrote was two years ago for a house deposit. I think the second last was 9 years before that for the deposit for our previous house.
I always try to have the absolute minimum in my client specs, but sometimes you do need to operate over the world.
The perforce docs are generally well written, worth looking at them.
https://www.blackducksoftware.com/solutions/mergers-and-acqu...
I'll now probably lose the next few hours panning around undersea cable maps. Again.
Broadcom had also acquired Netlogic/RMI before that, so it is consolidation all the way down.