To my knowledge, any other architecture targeted by GNU lightning offers more registers, so this magic number is effectively the largest number of registers one can offer where register allocation would become trivial for all architectures.
539 karma · joined July 9, 2014
Writing emulators and hypervisors.
Alexandro Sanchez <alexandro@phi.nz> https://phi.nz/
To my knowledge, any other architecture targeted by GNU lightning offers more registers, so this magic number is effectively the largest number of registers one can offer where register allocation would become trivial for all architectures.
Unsurprisingly, this has been done by Alibaba-owned T-Head Semiconductor. The obvious result if Chinese vendors start facing obstacles to obtain licenses to manufacture ARM-based chips (or any other non-Chinese architecture).
How can anyone expect that software/hardware-bans to global superpowers can result in anything but their software/hardware-independence in the long run?
If I'm biased, it might be because I defined the "cybersecurity industry" too broadly, not too narrowly: One can acquire certain skills from competing in CTFs/competitions, e.g. hard skills related to reverse engineering and vulnerability research... but I believe in most cases further skills are additionally needed to succeed in the industry, e.g. software engineering, and softer skills such as communication, planning and negotiation (useful for other jobs as well).
Overly optimizing skills to win CTFs while neglecting other matters can be harmful, like badly assigned character points in an RPG. :-)
Disclaimer: I don't have any data to back this up.
Decades ago, compiler developers solved dealing with multiple CPU architectures, by creating languages that succinctly expresses their common traits: Doing arithmetical-logical operations and accessing memory. Languages like C abstracted us from CPU registers, stacks. Optimization passes like vectorization abstracted us from different ISA extensions.
Now it feels it's the same issue all over again. Is it really hard to simply express: `x' = W*x + b` and let the compiler target the CPU/GPU/NPU as needed?
Please correct me if I'm mistaken (not a ML expert): On top of these existing APIs, we can build efficient neural networks. Of course, we wouldn't be able to use specialized hardware such as Google's TPU or Graphcore's IPU, but I doubt there's a use-case for those in web.
Is there any non-GPU/CPU based consumer hardware aimed at fast neural networks that I'm missing?
EDIT: Seems "NPU"s have been slowly arriving for the past 2 years to iOS/Android-based devices... Maybe there's a raison d'être for the WebNN API after all.
Simulations will always be as good as our computing power gets, and the results will be "understood" as good as our perception gets. So, in some sense, both scenarios are the same.
In practice, there's nothing that WebAssembly offers that could hinder analysis even further. If websites want to be transparent they could provide the sources (akin to providing unminified/unobfuscated JavaScript).
Can you elaborate more on this point? Links as to why this is impossible would be appreciated. If paint absorbs certain wavelengths while reflecting others (which are the perceived color), wouldn't the mixture of two colors absorb two subsets of the spectrum, and reflect everything else? And if so, why can't it be simulated?
Where would that be? On every trip to the US I have exchanged cash, EUR to USD, resulting in mostly $100 bills which I've used everywhere, sometimes even for rather small purchases, and there's been no frown upon that (after few purchases I also get my hands on smaller bills which are also more convenient).
If only it was that easy. With several governments regulating against cash, e.g. banning cash transactions above a certain amount, and limiting withdrawing/depositing cash in bank accounts, can we really say we have right of property (of money at least)? It seems yet another right to throw under the bus for the sake of mitigating "money laundering" and "terrorism".
The entire article is blocked behind that "rotating device" icon. Really terrible job.
The actual time to reach 6 km was around 6.5 minutes in the "typical flight" and around 5 minutes in the "test flight", as can be seen by scaling both graphs to the same proportions. (I've done it quickly with Paint here: https://i.imgur.com/IZyYoCl.png)
Is that 1.5 minute difference really that high? Honest question, I really don't know anything about this topic.
EDIT: Sorry, this should have been a reply to @rkagerer's comment.
Then again, this was just one of many variants of the simulation hypothesis, just something unfalsifiable that shouldn't be taken too seriously. :-)
But why would any of that matter? In the end it's just a blob of data, modified by some algorithm with every tick. That's not much different than computing 2+2=4. Does it matter whose computer calculated that? Will the answer be different if they pull the plug? None of that matters: maybe multiple beings are simulating the exact same universe, or maybe none of them are. Why would anything need to be computed "physically" to make the simulation happen?
This take on the simulation hypothesis is the main plot point of "Permutation City" by Greg Egan, which to this day, is (IMHO) the most reasonable variant of the hypothesis I have read.
True. This is an unimportant rant on my side, since it would be nice to have a complete emulator out-of-the-box. But it's true it can be solved in userspace (EDIT: now I wonder how could we inject exceptions back into the guest, should they occur during emulation in userspace).
> I'm curious what you mean about no guest debugging support.
This would allow the host to introduce software/hardware breakpoints and single-stepping through the guest. This is extremely relevant to debug bootloaders/microkernels, or in my case, closed-source kernels that do not support debugging. Some hypervisors, e.g. KVM (and soon HAXM), support this: check "KVM_DEBUG_GUEST" at https://www.kernel.org/doc/Documentation/virtual/kvm/api.txt
> Also curious about the other shortcomings so that we can prioritize appropriately.
The API provides no way to add/override/hook arbitrary MSRs while handling guests's rdmsr/wrmsr instructions, or override CPUID leaves/subleaves. This is required to run certain kernels are designed to run in specific x86 processors. Of course, most hypervisors lack this feature and I understand that WHPX is fairly recent so I'm not complaining about the lack of it. My issue is rather that closed-source implementations are not helpful for researchers since shortcomings like these means the whole library is no longer usable for us. Comparatively adding such features to (say) KVM or HAXM takes just few hours.
Also, don't get me wrong. I feel it's incredibly valuable having finally an API allowing developers benefit from Hyper-V in userland. I'm just concerned about the current trend of hypervisor APIs, as every vendor eventually just ships a closed hypervisor library for its own platform, and developers have to put up with 5 different ways of doing the same thing.
(PS: I've invested quite some time on HAXM, but I'm not affiliated with Intel in any way)
I'm afraid that the ecosystem of hypervisor APIs are going the same way as with graphics APIs, e.g. thanks to Direct3D and Metal. I believe we should disregard such APIs in favor of cross-platform open alternatives such as Intel's HAXM: Support for Linux and AMD SVM is planned on my side, as it serves as basis for my PS4 LLE emulator.
It's ridiculous making such mental gymnastics to stretch this article in order to blame "the West".
To be honest, this looks like a quarrel between baboons that have invested too much, and baboons that have shorted too much. I've never ever seen HN in such a state and hope to not see it.
I was, I've spent more Bitcoins than traditional currencies on buying actual products during last year (electronics, games, hotels, flight tickets, etc.). That ended, 1 months ago when fees rose to a point limit that made such relatively small operations inviable.
That said, I still hope for new cryptocurrencies to provide a solution to scalability issues. Maybe https://failsafe.network/ or maybe something else.
> Eero [...] has laid off 20 percent of its workforce (about 30 employees), TechCrunch has learned. Eero confirmed about 30 employees were let go but declined to comment on its total workforce size.
Since the workforce size can be inferred from this information (specifically, Eero seems to have gone from 150 to 120 employees approximately). Am I missing something, or why do they say Eero declined to comment on the workforce size? How did TechCrunch learn that those 30 employees represented 20% of the company workforce?
While quantum computers threaten some cryptographic schemes, it will just be the end of those schemes, not the end of cryptography in general (see: post-quantum cryptography). As long as we still have problems that are hard to compute and easy to verify, we can have cryptocurrencies. Quantum computers do not give "unlimited computing power" and do not threaten the existence of cryptocurrencies in general.
I have been spending plenty of mBTC in the stores (shopping, flights, hotels) that accept it such as Overstock, Abitsky, Destinia, etc. and my experience there has been way more comfortable than shopping with credit cards or even Paypal.
While such jobs require indeed people working on weekends, it doesn't mean that the workers themselves need to be present 7 days a week. It's possible to uniformly distribute 2 free days per week among workers and still guaranteeing 24/7 service.
> Those that lament its passing as some sort of societal shift show thier colours.
Not sure what "their colours" mean. Why should we lower our expectations to the lowest working conditions? Instead, why don't we all aspire to redistributing our working ours to ensure a fair share of free time.