Hacker News

points by florieger 16 hours ago | 0 comments

I wonder if this should trigger a warning (or even an error) at application startup whenever the CPU architectures differ.

IMHO, that would be much better than running into crashes and having to figure out the cause yourself.

[–] ahartmetz 1 hour ago

Standard operating procedure for caches: The cache key must contain all relevant criteria to decide whether the entry contains what you want. Code for a different architecture isn't it. In a VM that might get moved around, an extended cache key would solve a lot of problems, even preserving entries for other CPUs as long as there is space.

[–] odo1242 14 hours ago

Yea, it should probably warn and fallback to normal JIT

[–] jayd16 15 hours ago

Should probably just kick in the JIT at that point, no?