# Understanding JULIA\_CPU\_TARGET

**URL:** <https://discourse.julialang.org/t/understanding-julia-cpu-target/116774>\
**Category:** New to Julia\
**Tags:** precompilation\
**Created:** [July 8, 2024, 2:15pm UTC](https://discourse.julialang.org/t/understanding-julia-cpu-target/116774 "2024-07-08T14:15:40Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Sevi](https://avatars.discourse-cdn.com/v4/letter/s/c67d28/32.png) [@Sevi](https://discourse.julialang.org/u/Sevi)\
**Post date:** [July 8, 2024, 8:51pm UTC](https://discourse.julialang.org/t/understanding-julia-cpu-target/116774/5 "2024-07-08T20:51:53Z")

</div>

Just wanted to leave this link here in case it’s helpful. I had similar questions (but about the automatic package precompilation, not with sysimages, but the process is “similar” 😉 )

> [@Julia 1.9, same depot with different machines?](https://discourse.julialang.org/t/julia-1-9-same-depot-with-different-machines/103463):
>
> Hi! I’m using Julia 1.9 on an HPC cluster and ran into a strange error on some of the machines. I have a hunch that it’s related to native code caching and the fact that I currently use the same depot for all machines, but I’m a bit stuck investigating the actual issue and finding a good solution. Problem Running certain code on the affected machines gives an Illegal instruction error. So far I could only trigger the error when using Cthulhu.jl, but I’m not sure if it’s really related to that p…

The upshot is that I also ended up using `generic` followed by the CPU architectures returned from `Sys.CPU_NAME` which I crawled on our cluster with a short script, so something like

`generic;sandybridge;icelake-server;znver2;haswell;broadwell;znver1;skylake-avx512;znver3;cascadelake`

---

_[View the full topic](https://discourse.julialang.org/t/understanding-julia-cpu-target/116774)._