Re:Apple announces it will switch to its own processors for ...
by mantap on Monday June 22, 2020 @03:03PM
(#23604459)
They explicitly said that it can perform both static and dynamic translation for JITs. I wouldn't be surprised if there is substantial hardware support too.
[ Parent
| on HN ]
Re:Apple announces it will switch to its own processors for ...
by mrkstu on Monday June 22, 2020 @03:24PM
(#23604927)
My brain skipped over that part apparently. It is interesting that they are calling out virtualization improvements separately though.
Re:Apple announces it will switch to its own processors for ...
by saagarjha on Monday June 22, 2020 @03:46PM
(#23605366)
Apple's chips haven't supported that yet, so it's certainly something new.
Re:Apple announces it will switch to its own processors for ...
by vletal on Monday June 22, 2020 @04:28PM
(#23606093)
I was wondering why did they mention the virtualization. Let's see what technology do they use. Whether it is going to be proprietary or something like Xen.
Re:Apple announces it will switch to its own processors for ...
by thetinguy on Tuesday June 23, 2020 @07:08PM
(#23621541)
In the state of the union they mentioned an Apple hypervisor
Re:Apple announces it will switch to its own processors for ...
by monocasa on Monday June 22, 2020 @09:21PM
(#23608990)
It's going to be an ARM clone of Hypervisor.Framework.
Re:Apple announces it will switch to its own processors for ...
by SahAssar on Monday June 22, 2020 @07:14PM
(#23608068)
> They explicitly said that it can perform both static and dynamic translation for JITs
Can a JIT be static? Isn't that not possible by definition?
Re:Apple announces it will switch to its own processors for ...
by mantap on Tuesday June 23, 2020 @05:57AM
(#23611839)
I meant that it supports dynamic translation in order to support JITs such as turbofan.
But to answer your question, yes a JIT can be static. JIT just means that the compilation happens at runtime, and "static" in this context means that the compilation is happening at the very start of runtime. You could imagine a JIT that compiles all bytecode to native code immediately on launch. The reason this technique is not used often is that it tends to lead to long startup times. But if the result is cached somewhere then it might be acceptable.