[External] : Re: AOT code usage restrictions

[Andrew Haley]

On 26/01/2026 09:01, María Arias de Reyna Dominguez wrote:
> My two cents: it makes sense to make the "native" the default mode, because
> that's the one people should use. Because it is the one that gets more
> juice from your app. Because it is the one that makes most sense if you
> want to improve startup and warmup times.

But that is to raise the question of what exactly does "native" mean? 
For example, there is a bug in early steppings of a particular core. To 
work around the bug today, we detect exactly which core we're running on 
and generate instructions that aren't affected by that bug.

I don't believe there can be any "correct" answer to this. In practice I 
suppose we'd default to safe, because Java devrel people can't be 
expected to know about finer details of CPU core versions. But it does 
mean that we can't always run at maximum performance with AOT 
compilation, even with "native" mode.

Andrew.