about summary refs log tree commit diff
path: root/pkgs/development/compilers/llvm/13
AgeCommit message (Collapse)AuthorFilesLines
2023-10-30llvmPackages_12.openmp,llvmPackages_13.openmp: fix crossAlyssa Ross1-0/+11
CMake commit faa950a155 ("try_compile: Run native build tool with verbose output") did not play well with these versions of openmp, which have a faulty failure regex that considers "unknown" in the build output to indicate a failure. When cross compiling, the string "unknown" is very likely to occur as part of triples. Fix by backporting a patch that improves the failure regex check to not be tripped up by triples. The same problem affects LLVM 11 and possibly earlier, but the patch doesn't apply that far back, so I didn't bother for now. Fixes: b8ac5b6cfbc7 ("cmake: 3.25.3 -> 3.26.4")
2023-09-08treewide: replace -DCMAKE_BUILD_TYPE in cmakeFlags with cmakeBuildTypeSandro Jäckel1-1/+2
2023-09-07Merge staging-next into staginggithub-actions[bot]1-1/+2
2023-09-06Merge pull request #236203 from SharzyL/llvm_no_extendArtturi1-1/+2
2023-09-06Merge pull request #253533 from Artturin/llvmusesuballArtturi1-7/+8
2023-09-06Merge pull request #253573 from Artturin/llvmdedup2Artturi2-17/+1
2023-09-06llvmPackages.lldb: remove unnecessary inheritArtturin1-1/+1
release_version is provided with callPackage
2023-09-06llvmPackages.libcxxabi: dedupe `wasm.patch`Artturin2-17/+1
found with fdupes ``` pkgs/development/compilers/llvm/8/libcxxabi/wasm.patch pkgs/development/compilers/llvm/13/libcxxabi/wasm.patch pkgs/development/compilers/llvm/14/libcxxabi/wasm.patch pkgs/development/compilers/llvm/10/libcxxabi/wasm.patch pkgs/development/compilers/llvm/15/libcxxabi/wasm.patch pkgs/development/compilers/llvm/12/libcxxabi/wasm.patch pkgs/development/compilers/llvm/9/libcxxabi/wasm.patch pkgs/development/compilers/llvm/16/libcxxabi/wasm.patch pkgs/development/compilers/llvm/git/libcxxabi/wasm.patch pkgs/development/compilers/llvm/11/libcxxabi/wasm.patch ```
2023-09-06llvmPackages.bintools-unwrapped: deduplicateArtturin2-36/+1
2023-09-06llvmPackages.lldb: use substituteAllArtturin1-6/+7
2023-08-04Merge master into staging-nextgithub-actions[bot]8-8/+8
2023-08-03treewide: noop: refer to `src.name` or similar in `sourceRoot` where ↵Jan Malakhovski8-8/+8
appropriate, part 1: trivial cases
2023-07-18Merge pull request #191801 from ShamrockLee/clang-python-scan-view7c6f434c1-1/+2
clang-unwrapped: mv {$out,$python}/share/scan-view/*.py
2023-06-20Merge staging-next into staginggithub-actions[bot]2-164/+30
2023-06-20Merge pull request #230387 from Artturin/llvmsplit1Artturi2-164/+30
2023-06-06llvmPackages: remove `extend` attributeSharzyL1-1/+2
2023-05-30llvm_{10..13}: backport gcc-13 fixesSergei Trofimovich1-0/+14
Without the change `llvm` build fails on `gcc-13` fails as: [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Signals.cpp.o In file included from llvm/lib/Support/Signals.cpp:14: llvm/include/llvm/Support/Signals.h:119:8: error: variable or field 'CleanupOnSignal' declared void 119 | void CleanupOnSignal(uintptr_t Context); | ^~~~~~~~~~~~~~~
2023-05-09llvmPackages.lldb: deduplicate >10Artturin2-164/+30
2023-05-08Merge staging-next into staginggithub-actions[bot]1-1/+1
2023-05-08llvm: fix typosfetsorn1-1/+1
"verion" -> "version"
2023-05-03llvm_13: backport patch for musl 1.2.4Alyssa Ross1-0/+7
2023-04-28pkgsLLVM.stdenv: use clangNoLibc when libc is nullAlyssa Ross1-1/+2
clangNoLibc always uses LLVM bintools, so it still has the useLLVM semantics.
2023-04-28compiler-rt: use -ffreestanding when no libcAlyssa Ross1-2/+4
This fixes building for x86_64-windows with no libc (for UEFI). Otherwise, it would try to include a malloc header.
2023-04-12Revert "llvmPackages_13.compiler-rt-libc: also apply tmp hack"Adam Joseph1-1/+1
This reverts commit 9bf18e069e9c5455b7759f9b6e2ee8ebedff2279.
2023-04-12Revert "cc-wrapper: add optional temporary hack for -B"Adam Joseph1-2/+1
This reverts commit ac3acd956f730fa9870d4488c91699c8e2892a39.
2023-04-12llvmPackages_13.compiler-rt-libc: also apply tmp hackVladimír Čunát1-1/+1
This part got forgotten in commit ac3acd956f730fa98.
2023-04-12cc-wrapper: add optional temporary hack for -BVladimír Čunát1-1/+2
This fixes parts in llvmPackages_{13,rocm} e.g. build .clang for testing. Longterm mass-rebuild fix should come in PR #225846
2023-03-13Merge pull request #205176 from lopsided98/compiler-rt-armv67c6f434c1-0/+6
compiler-rt: fix build on ARMv6
2023-03-11Merge staging-next into staginggithub-actions[bot]1-1/+11
2023-03-10Merge remote-tracking branch 'origin/master' into staging-nextAlyssa Ross1-1/+11
Conflicts: pkgs/development/libraries/librsvg/default.nix pkgs/development/python-modules/r2pipe/default.nix
2023-03-10llvmPackages.compiler-rt: enable libclang_rt.profile-....a buildAlyssa Ross1-1/+2
Port of 94cad6ec1ad ("llvm 14 compiler-rt: enable libclang_rt.profile-....a build").
2023-03-10llvm: add in a missing check depAlyssa Ross1-3/+27
Port of 6d0c87602fe ("llvmPackages_15.llvm: add in a missing check dep"). I did not include the sysctl nativeCheckInputs change from that commit, as it looks like it was included by mistake and was supposed to be in c7231c0b6d8 ("llvmPackages_15.llvm: run the tests on macOS"). I've also included the doCheck default from that commit (without the change to run on non-Linux), as 6d0c87602fe just set it to true.
2023-03-10clang: drop the C++ std version `-DCMAKE_CXX_FLAG`Alyssa Ross1-1/+0
Port of 404ef6b6c92 ("llvmPackages_15.clang: drop the C++ std version `-DCMAKE_CXX_FLAG`"). The commit mentioned as removing the need for the override[1] first appeared in LLVM 10. [1]: https://github.com/llvm/llvm-project/commit/2724d9e12960cc1d93eeabbfc9aa1bffffa041cc
2023-03-08compiler-rt: fix build on ARMv6Ben Wolsieffer1-0/+6
compiler-rt has accumulated several regressions that prevent it from building on ARMv6. It is important to note that there are two major versions of ARMv6: base ARMv6 and ARMv6K. ARMv6K includes several important new instructions, such as non-word size atomic operations (ldrexd, strexd, etc.) and the yield instruction. Most ARMv6 CPUs actually implement ARMv6K, including all those used in Raspberry Pis, but nixpkgs' "raspberryPi" platform targets base ARMv6. compiler-rt versions 8-14 fail to build on ARMv6 and ARMv6K. compiler-rt 15 (not yet in nixpkgs) builds on ARMv6K but not ARMv6. This patch fixes versions 9-14 on both ARMv6 variants. The patches don't apply cleanly to version 8, and I figured it wasn't worth carrying another version of the patches for such an old version. A total of five patches are required to get compiler-rt building on ARMv6: * armv6-mcr-dmb.patch: use `mcr` to provide the equivalent of `dmb` on ARMv6. Included in LLVM 15. * armv6-sync-ops-no-thumb.patch: prevent certain atomic operation functions from using Thumb mode. Included in LLVM 15. * armv6-no-ldrexd-strexd.patch: don't use ldrexd or strexd, which are not available in base ARMv6. Submitted upstream by me. * armv6-scudo-no-yield.patch: use nop instead of yield on ARMv6 in standalone scudo. Required by versions >=13, since they enable standalone scudo. Submitted upstream by me. * armv6-scudo-libatomic.patch: link standlone scudo to libatomic on ARMv6 (and any other platforms that need it). Not yet submitted because the backport is a bit different from the upstream version and I need to test it.
2023-03-03llvm: tighten platformsAlyssa Ross1-1/+11
LLVM can't be built for all architectures supported by Nixpkgs (s390, and for some versions m68k and RISC-V).
2023-03-02llvmPackages*.clang_manpages: drop the sphinx `find_package` patchRahul Butani1-3/+0
This is a backport of f8cbbdd05b167185fdcabd5f494daa02215667b3. LLVM versions >= 5.0.0 already look for sphinx when `LLVM_ENABLE_SPHINX` is enabled: https://github.com/llvm/llvm-project/commit/ea139eccc1770a626b71fdd278d368bb49b6734c
2023-02-28lld: explain why we change the stack size on MuslAlyssa Ross1-0/+2
Suggested-by: Rahul Butani <rrbutani@users.noreply.github.com>
2023-02-28lld: build with 2M stack sizeAlyssa Ross1-0/+1
Port of 6485a02fb3c ("llvm 14 lld: build with 2M stack size to fix firefox lto").
2023-02-28Merge staging-next into staginggithub-actions[bot]1-2/+2
2023-02-28llvm*: Remove `outputSpecified` workaround where possibleRobert Hensing1-2/+2
The effect of `.out // { outputSpecified = false; }` in these cases is to select the default output explicitly, but then make the selection implicit until `overrideAttrs` is called. Previously `overrideAttrs` would not preserve output selection, masking the apparently unnecessary behavior of this workaround. For `libllvm-polly`, this logic does not apply, as it does not select the default output. The `outputSpecified` workaround was introduced in https://github.com/NixOS/nixpkgs/pull/122554 and was perhaps rushed because of a release deadline, and expected delays from mass rebuilds. The change in `overrideAttrs` behavior was added in 5b2f597b116d56104d45c35587920323ed2a5666 / https://github.com/NixOS/nixpkgs/pull/211685 and the problem was discovered in https://github.com/NixOS/nixpkgs/pull/218537, which may contain further information.
2023-02-26clang_13,clang_14,clang_git: deduplicate patchAlyssa Ross2-19/+1
The same patch applies to all Clang versions using it.
2023-02-23Merge staging-next into staginggithub-actions[bot]1-1/+1
2023-02-22treewide: move NIX_CFLAGS_COMPILE to the env attrsetArtturin1-1/+1
with structuredAttrs lists will be bash arrays which cannot be exported which will be a issue with some patches and some wrappers like cc-wrapper this makes it clearer that NIX_CFLAGS_COMPILE must be a string as lists in env cause a eval failure
2023-02-22treewide: use toString on list NIX_CFLAGS_COMPILEArtturin1-1/+1
with structuredAttrs lists will be bash arrays which cannot be exported which will be a issue with some patches and some wrappers like cc-wrapper
2023-02-16Merge pull request #212498 from risicle/ris-fortify3Robert Scott1-1/+2
hardening flags: add `FORTIFY_SOURCE=3` support
2023-02-13treewide: use optionalStringFelix Buehler1-5/+2
2023-02-04Merge master into staging-nextgithub-actions[bot]1-0/+3
2023-02-04Merge pull request #207863 from patryk4815/fix-lldb7c6f434c1-0/+3
lldb_14: fix broken python3 site-packages and lua5_3
2023-01-30binutils: consolidate plugin-api.h support in a singleSergei Trofimovich1-1/+2
I got the plugin API support at least once incorrect. Instead of copying the deifnition let's consolidate it within binutils itself. While at it forward-ported changes to llvm_{13,14,15}. The change is a no-op from rebuild perspective.
2023-01-24llvm*Packages.clang: mark hardeningUnsupportedFlags fortify3Robert Scott1-1/+2
it's very unclear what the status of FORTIFY_SOURCE=3 support in clang is
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-09 04:46:00 +0000