aboutsummaryrefslogtreecommitdiff
path: root/packages/gcc
Commit message (Collapse)AuthorAgeFilesLines
* gcc-14.2: Fix ICE on aarch64BtbN2024-08-226-0/+781
| | | | | | | See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115464 for issue description and list of patches to backport. Signed-off-by: BtbN <btbn@btbn.de>
* gcc: Add 14.2.0Chris Packham2024-08-0515-27/+22
| | | | | | | | https://gcc.gnu.org/pipermail/gcc-announce/2024/000184.html Add the new version clean up the patches. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Add 11.5Chris Packham2024-07-2934-2877/+27
| | | | | | | | https://gcc.gnu.org/pipermail/gcc-announce/2024/000183.html Add the new version drop the patches that have been applied upstream. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Add GCC 12.4.0Chris Packham2024-06-2734-3080/+31
| | | | | | | | | https://gcc.gnu.org/pipermail/gcc-announce/2024/000182.html Add the new version dropping patches that have been applied upstream. Fixes #2175 Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Add GCC 13.3.0Chris Packham2024-05-2440-3239/+165
| | | | | | | | https://gcc.gnu.org/pipermail/gcc-announce/2024/000181.html Add the new version dropping patches that have been applied upstream. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* Initial GCC 14.1.0 supportNik Konyuchenko2024-05-1815-1/+872
| | | | | | | | + gcc 14 package version + tar.gz and tar.xz checksums + patches from gcc13 that can still be applied to gcc14 Signed-off-by: Nik Konyuchenko <spaun2002mobile@gmail.com>
* gcc/13.2.0: Fix musl libdir path for loongarch64WANG Rui2024-03-093-0/+169
| | | | | | | | | | This patch adds two gcc commits to fix musl libdir path for loongarch64: * 13c5de14 ("LoongArch: Fix MUSL_DYNAMIC_LINKER") * a5f1bdfc ("LoongArch: Modify MUSL_DYNAMIC_LINKER.") * 2f7d4728 ("LoongArch: Use /lib instead of /lib64 as the library search path for MUSL.") Signed-off-by: WANG Rui <wangrui@loongson.cn>
* gcc: Add patch to resolve libsanitizer build issueChris Packham2024-01-302-0/+270
| | | | | | | | | | | | libsanitizer has problems intercepting crypt() and crypt_r() with newer glibcs. Bring in an upstream patch that drops support for these from ASAN. llvm/llvm-project@d7bead8 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111057 Fixes #2083 Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Bring in upstream fixes for CVE-2023-4039crosstool-ng-1.26.0-rc2Chris Packham2023-09-17100-0/+15138
| | | | | | | | | Bring in the fixes for GCC 7 through 13. https://rtx.meta.security/mitigation/2023/09/12/CVE-2023-4039.html https://developer.arm.com/Arm%20Security%20Center/GCC%20Stack%20Protector%20Vulnerability%20AArch64 Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Add patch to avoid reference to __pthread_key_createChris Packham2023-09-131-0/+35
| | | | | | | | | | | | | | | | A toolchain uclibc-ng-1.0.43, binutils-2.40 and gcc-13.2.0 hits the following error when building: ld.bfd: isl_test2.o: non-canonical reference to canonical protected function `__pthread_key_create' in x86_64-multilib-linux-uclibc/sysroot/lib64/libc.so.1 ld.bfd: failed to set dynamic section sizes: bad value The reference comes from libgcc where it is using the __pthread_key_create() symbol to detect the use of pthreads with GNU libc. Prevent this on uclibc-ng with an explicit condition. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111322 Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc/13.2.0: Add patch with fixes for m68k soft float codecrosstool-ng-1.26.0-rc1Keith Packard2023-08-251-0/+348
| | | | | | | Here's a patch I've sent upstream which fixes a range of floating point bugs in libgcc. Signed-off-by: Keith Packard <keithp@keithp.com>
* gcc: Add patch to resolve libsanitizer build issueChris Packham2023-08-191-0/+141
| | | | | | | | | | | | libsanitizer has problems intercepting crypt() and crypt_r() with newer glibcs. Bring in an upstream patch that drops support for these from ASAN. https://github.com/llvm/llvm-project/commit/d7bead833631486e337e541e692d9b4a1ca14edd https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111057 Fixes #2010 Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Add 13.2.0Chris Packham2023-08-0415-9/+9
| | | | | | | | | https://gcc.gnu.org/pipermail/gcc-announce/2023/000179.html https://gcc.gnu.org/gcc-13/changes.html Add the new version and regenerate the patches. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Update 10.4 -> 10.5Chris Packham2023-07-1427-27/+19
| | | | | | | | | Add GCC 10.5.0 and regenerate patches against the new version. https://gcc.gnu.org/pipermail/gcc-announce/2023/000178.html https://gcc.gnu.org/gcc-10/changes.html Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Add 11.4.0Chris Packham2023-05-3114-25/+17
| | | | | | | | | Add gcc 11.4.0 and regenerate patches against the new version. https://gcc.gnu.org/pipermail/gcc-announce/2023/000177.html https://gcc.gnu.org/gcc-11/changes.html Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc/6.5.0: Bring in upstream fix for newer ISL versionsChris Packham2023-05-281-0/+221
| | | | | | | | | | | | | | | | | isl-0.26 moves some header includes around so now if we want isl_val_free we need to include isl/val.h. Otherwise we get errors such as src/gcc/gcc/graphite-isl-ast-to-gimple.c: In member function 'tree_node* translate_isl_ast_to_gimple::gcc_expression_from_isl_expr_int(tree, isl_ast_expr*)': src/gcc/gcc/graphite-isl-ast-to-gimple.c:349:3: error: 'isl_val_free' was not declared in this scope; did you mean 'isl_vec_free'? 349 | isl_val_free (val); | ^~~~~~~~~~~~ | isl_vec_free Bring in an upstream fix that uses the correct header file. Fixes #1962 Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc/6.5.0: Regenerate patchesChris Packham2023-05-283-35/+37
| | | | | | | Run patches through ./maintainer/manage-packages.sh -P -s gcc-6.5.0 to clean them up. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Add upstream patch for build issue on RISCVChris Packham2023-05-141-0/+41
| | | | | | | | | | | | | | | | | Depending on the host C++ compiler GCC13 fails on riscv configurations with the following error src/gcc/gcc/config/riscv/genrvv-type-indexer.cc:118:30: error: no member named 'log2' in namespace 'std'; did you mean simply 'log2'? elmul_log2 = lmul_log2 - std::log2 (sew / eew); ^~~~~~~~~ log2 /usr/include/c++/v1/math.h:1463:1: note: 'log2' declared here log2(_A1 __lcpp_x) _NOEXCEPT {return ::log2((double)__lcpp_x);} ^ Bring in an upstream fix for the build error. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Add 13.1.0Chris Packham2023-05-1414-1/+837
| | | | | | | | | | Add gcc 13.1.0 with rebased patches against the new version. https://gcc.gnu.org/pipermail/gcc-announce/2023/000175.html https://gcc.gnu.org/gcc-13/changes.html https://gcc.gnu.org/gcc-13/porting_to.html Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Add 12.3.0Chris Packham2023-05-1414-21/+21
| | | | | | | | | Add gcc 12.3.0 and regenerate patches against the new version. https://gcc.gnu.org/pipermail/gcc-announce/2023/000176.html https://gcc.gnu.org/gcc-12/changes.html Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc/12.2.0: Regenerate patchesChris Packham2023-04-305-53/+21
| | | | | | | | | | Run the patches through ./maintainer/manage-packages.sh -P -s gcc-12.2.0 to mop up the fact that we'd ended up with two 0005 patches. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* [gcc] Move a patch to the bundled experimental patchesBryan Hundven2023-03-161-0/+0
| | | | | | | | | | | | As mentioned in #1908, we should have patches that are experimental under the CT_EXPERIMENTAL option. This an experimental patch to gcc: https://gcc.gnu.org/pipermail/gcc-patches/2022-August/600452.html And since it may affect production toolchains, we should move this patch to the experimental bundled patches introduced in the previous commit. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
* Support targeting macOS aarch64 in older GCCsSteven Fackler2023-03-1411-0/+506
| | | | | | | | | This adds backports of a couple of patches necessary to support macOS arm64 hosts for gcc. It was ported from https://github.com/richfelker/musl-cross-make/pull/129 with some small fixups to make the patches apply cleanly. Signed-off-by: Steven Fackler <sfackler@gmail.com>
* Merge pull request #1908 from keith-packard/gcc-getenv-defaultBryan Hundven2023-03-091-0/+102
|\ | | | | packages/gcc: Add gcc patch to allow getenv default values
| * packages/gcc: Add gcc patch to allow getenv default valuesKeith Packard2023-02-281-0/+102
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch, submitted upstream but not (yet?) accepted, adds a third parameter to the specs file 'getenv' function that provides a value for when the environment variable is not set, instead of having gcc fail. This seemed like the safest way to provide a mechanism for getting the installed location of the toolchain from inside a specs file as, when not installed in the built-in location, gcc already sets the GCC_EXEC_PREFIX environment variable to a well defined location within that directory hierarchy, but when installed in the location specified at compile time, gcc does not. Providing a default value that matches the compile-time location then allows the specs file to compute paths relative to the current GCC installation location, whereever it is installed. Signed-off-by: Keith Packard <keithp@keithp.com>
* | packages/gcc/12.2.0: Add picolibc patchesKeith Packard2023-03-085-0/+427
|/ | | | | | These patches allow picolibc to act as the system C library within gcc. Signed-off-by: Keith Packard <keithp@keithp.com>
* Backport fixes for glibc and gcc to fix interactions with kernel headersBryan Hundven2022-11-092-0/+246
| | | | | Reported-by: milkylainen (IRC) Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
* gcc: Add gcc 12.2.0Chris Packham2022-08-238-8/+8
| | | | | | | | https://gcc.gnu.org/pipermail/gcc-announce/2022/000174.html Add gcc 12.2.0. None of the patches needed regenerating. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Add gcc 10.4.0Chris Packham2022-07-1127-80/+21
| | | | | | | | | | | | https://gcc.gnu.org/pipermail/gcc-announce/2022/000173.html Add GCC 10.4.0 and regenerate the ct-ng patches. The powerpc-Fix-asm-machine-directive-for-some-CPUs patch is dropped as the change was applied upstream (and subsequently refactored). Closes #1777 Signed-off-by: Chris Packham <judge.packham@gmail.com>
* Revert "gcc: Bring in fix for libsanitizer on mips64"Chris Packham2022-07-111-31/+0
| | | | | | | | | This reverts commit 1b6ad7cd48e0849072e2372826498c01b56b7fc9. As it turns out libsanitizer isn't supported on mips64 with GCC11 or older (there is support in GCC12). The bug is actually the fact that ct-ng allows configuring libsanitizer for architectures that don't support it. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Add gcc 9.5.0Chris Packham2022-06-0822-11/+11
| | | | | | Add GCC 9.5.0 and regenerate the patches as necessary. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Update fix for sh-unknown-elfChris Packham2022-05-311-64/+0
| | | | | | | | | Extend the fix from commit 6b465e15 ("Remove m1 from multilibs for GCC11 on SH arch.") to cover GCC 12 and future releases. Remove the patch that was added to solve the same problem. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: drop libsanitizer patch for GCC12Chris Packham2022-05-232-26/+0
| | | | | | | | | | | For some reason GCC 12 ends up hitting the _MIPS_SIM_NABI32 case for Linux's arch/mips/include/uapi/asm/stat.h when building libsanitizer. This is basically the opposite of the problem from commit 1b6ad7cd ("gcc: Bring in fix for libsanitizer on mips64"). Dropping the patch resolves the issue for GCC 12. Fixes #1741 Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Add 12.1Chris Packham2022-05-1910-1/+441
| | | | | | | | | | | | | | | | | | | Add GCC 12.1 https://gcc.gnu.org/gcc-12/ The following patches from GCC 11.3.0 are no longer needed: - 0005-arc-Update-ZOL-pattern.patch - 0006-arc-Update-u-maddhisi4-patterns.patch - 0007-arc-Fix-maddhisi-patterns.patch - 0008-Darwin-aarch64-Initial-support-for-the-self-host-dri.patch - 0009-libstdc-Check-for-TLS-support-on-mingw-cross-compile.patch One new patch is needed to avoid issues building sh-unknown-elf: - 0006-sh-Avoid-mb-m1-multilib-combination.patch It is also necessary to build all-build-libcpp. This target exists as far back as GCC 6 so has been done unconditionally. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Bring in fix for libsanitizer on mips64Chris Packham2022-05-181-0/+31
| | | | | | | | | The kernel's struct stat is 104 bytes when compiling for _MIPS_SIM_ABI64. Set struct_kernel_stat_sz to match. Fixes #1733 Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Update vcs URLChris Packham2022-05-081-1/+1
| | | | | | | The GCC project has been using git for a while now. Update the repository field accordingly. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: bump GCC 11 to latest release 11.3.0Hans-Christian Noren Egtvedt2022-05-0817-460/+12
| | | | | | Remove patches applied upstream we no longer need to maintain here. Signed-off-by: Hans-Christian Noren Egtvedt <hegtvedt@cisco.com>
* gcc: add fixes for GCC 11.2. Anon and aggregated struct accessAnton Maklakov2022-03-282-0/+311
|
* gcc: rename patches to orderAnton Maklakov2022-03-281-0/+0
|
* gcc: powerpc: Fix asm machine directive for some CPUscrosstool-ng-1.25.0-rc1Chris Packham2022-02-282-0/+118
| | | | | | | Bring in upstream fix for gcc outputting an incorrect .machine directive. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* Fix MinGW libstdc++ TLS functionalityivanka20122022-02-281-0/+251
| | | | | | Backport of https://github.com/gcc-mirror/gcc/commit/cc1e28878a228b6c4a0872e56d97ac88971b7725 Signed-off-by: Kittenberger Iván <ivanka2012@gmail.com>
* Run patches thru `manage-packages -P`Alexey Neyman2022-02-1143-279/+190
| | | | | | | | This refreshes the line numbers, removes any fuzz (which would make any future forward ports easier) and standardizes the patch/file headers (which makes them easier to read). Signed-off-by: Alexey Neyman <stilor@att.net>
* Run packages through `manage-packages -D`Alexey Neyman2022-02-111-4/+4
| | | | | | | This fixed some typos in the checksum files (please don't edit them manually, this is error-prone!) Signed-off-by: Alexey Neyman <stilor@att.net>
* Retire obsoleted milestonesAlexey Neyman2022-02-111-1/+1
| | | | | | | | | | | | ... and the code dependent on them, after the latest wave of obsolete package removals. This concludes the glorious history of the original uClibc (non-NG) with lots of kludges removed. There was a choice here, whether to call the resulting libc "uClibc" or "uClibc-ng". I opted in favor of giving uClibc-ng the recognition it deserves, although it had some ripple effect in the ct-ng code. Signed-off-by: Alexey Neyman <stilor@att.net>
* Remove gcc-oracle-4.8-44.0.5Alexey Neyman2022-02-112-0/+38
| | | | | | | | | | | | | GCC 4.8 and its prerequisites have been removed by 04dce680, 41d4583a and e4221734; as a result, 4.8-based version of gcc-oracle became unbuildable (no valid versions for the prerequisites). Update the samples to use 4.9.4; which however fails to build on a modern host GCC. Build fix backported to gcc-4.9 and gcc-5 versions. Fix binutils-oracle build with host GCC11. Signed-off-by: Alexey Neyman <stilor@att.net>
* gcc: Use upstream fix for cross-canadian buildsChris Packham2022-01-142-47/+78
| | | | | | Replace the patch from #1600 with the change that landed upstream. Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Fix 11.2.0 build failure on MacOS with Apple M1Kairui Song2021-12-131-0/+99
| | | | | | | | | | | | | | | | | | | | | | | With latest aarch64-unknown-linux-gnu, ct-ng build failed with: [INFO ] Installing pass-1 core C gcc compiler [EXTRA] Configuring core C gcc compiler [EXTRA] Building gcc [ERROR] clang: error: linker command failed with exit code 1 (use -v to see invocation) [ERROR] make[2]: *** [Makefile:2148: xgcc] Error 1 [ERROR] make[2]: *** Waiting for unfinished jobs.... [ERROR] clang: error: linker command failed with exit code 1 (use -v to see invocation) [ERROR] make[2]: *** [Makefile:2157: cpp] Error 1 [ERROR] make[1]: *** [Makefile:4444: all-gcc] Error 2 And in build log: Undefined symbols for architecture arm64: "host_detect_local_cpu(int, char const**)", referenced from: static_spec_functions in gcc.o Just backport a upstream gcc fix. Signed-off-by: Kairui Song <ryncsn@gmail.com>
* gcc11: Fixes for ARCAlexey Brodkin2021-10-103-0/+285
| | | | | | | | | See more details here: 1. https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/issues/398 2. https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/issues/427 3. https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/issues/429 Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
* gcc: Remove obsolete versionsChris Packham2021-09-2130-2575/+0
| | | | | | | | | The following versions were marked obsolete in crosstool-ng-1.24.0, remove them. - gcc-linaro-4.8-2015.06 - gcc-4.8.5 Signed-off-by: Chris Packham <judge.packham@gmail.com>
* gcc: Fix cross-canadian builds wih GCC11Alexey Brodkin2021-09-151-0/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | With this we may finally build Windows and "native" toolchains if host tools are also GCC11 based. For example: 1. You build cross toolchain with all the recent components by CT-NG 2. You build cross-canadian toolchain for Windows or ARC, ARMm whatever board See upstream bug report [1] for more details. Basically when we do cross-canadian build with use of the same GCC11 as a "host" compiler we're seeing an error like that: ------------------->8------------------- mingw-w64-cross/gcc/x86_64-w64-mingw32/libstdc++-v3/include/fenv.h:58:11: error: 'fenv_t' has not been declared in '::' 58 | using ::fenv_t; ------------------->8------------------- This is a solution proposed by Yujie Yang in [2] Note, though it's not the final fix merged upstream, that's just an attempt to fix this by casual GCC users. There's a hope it will be fixed anyways a bit later, maybe by the time of GCC 11.3... [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017 [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100017#c20 Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-08 06:07:53 +0000