# Cpu\_target of standard Windows 64-bit download

**URL:** <https://discourse.julialang.org/t/cpu-target-of-standard-windows-64-bit-download/2885>\
**Category:** General Usage\
**Created:** [March 26, 2017, 10:42am UTC](https://discourse.julialang.org/t/cpu-target-of-standard-windows-64-bit-download/2885 "2017-03-26T10:42:18Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![joaquimg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joaquimg/32/223_2.png) [@joaquimg](https://discourse.julialang.org/u/joaquimg)\
**Post date:** [October 6, 2017, 5:39pm UTC](https://discourse.julialang.org/t/cpu-target-of-standard-windows-64-bit-download/2885/5 "2017-10-06T17:39:05Z")

</div>

I am using the julia-0.5.1 option:  
`-C, --cpu-target <target> Limit usage of cpu features up to <target>` inside [BuildExecutable.jl](https://github.com/dhoegh/BuildExecutable.jl)

turns out that compiling in **Windows10 (with Intel(R) Core™ i7-5500U CPU @ 2.40GHz)** with `cpu_target` `"core2"`, `"x86-64"`,` "generic"`

seem to cause:

`LLVM ERROR: Program used external function 'rint' which could not be resolved!`

in a **Windows Server 2012 R2 (Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz)**

Yes, compiling in one machine and running in another.

`"generic"` also causes:

`WARNING: unable to determine host cpu name`

Moreover, compiling with `"native"` works locally in both machines.

this issue is related to [https://github.com/dhoegh/BuildExecutable.jl/issues/47](https://github.com/dhoegh/BuildExecutable.jl/issues/47)

---

_[View the full topic](https://discourse.julialang.org/t/cpu-target-of-standard-windows-64-bit-download/2885)._