Issue description
|
apple-m1 = { |
|
gcc = { |
|
arch = "armv8.3-a+crypto+sha2+aes+crc+fp16+lse+simd+ras+rdm+rcpc"; |
|
cpu = "apple-a13"; |
|
}; |
|
}; |
adds inappropriate arch args for apple-m1. According to Apple clang, arch = "armv8.5a+fp-armv8+neon+crc+crypto+dotprod+fp16fml+ras+lse+rdm+rcpc+zcm+zcz+fullfp16+sm4+sha3+sha2+aes";.
(The string isn't even correct for apple-13 AFAICT, it's armv8.4a.)
Is there any reason against setting arch to the string above?
Secondly, is there any reason against setting cpu = "apple-m1"; once llvm12 is default? llvm11 doesn't support that cpu type; what would happen if a package's llvm was overridden to be llvm11?
cc @thefloweringash @NixOS/darwin-maintainers
Issue description
nixpkgs/lib/systems/platforms.nix
Lines 393 to 398 in dd697d4
adds inappropriate
archargs for apple-m1. According to Apple clang,arch = "armv8.5a+fp-armv8+neon+crc+crypto+dotprod+fp16fml+ras+lse+rdm+rcpc+zcm+zcz+fullfp16+sm4+sha3+sha2+aes";.(The string isn't even correct for
apple-13AFAICT, it'sarmv8.4a.)Is there any reason against setting
archto the string above?Secondly, is there any reason against setting
cpu = "apple-m1";once llvm12 is default? llvm11 doesn't support that cpu type; what would happen if a package's llvm was overridden to be llvm11?cc @thefloweringash @NixOS/darwin-maintainers