staging/dangole/toolchain/gcc, branch main

toolchain: gcc: update to 13.3

2024-05-28T21:55:27Z

Release Notes: https://gcc.gnu.org/pipermail/gcc/2024-May/243980.html Remove upstreamed patches: - patches-13.x/020-Include-safe-ctype.h-after-C-standard-headers-to-avo.patch - patches-13.x/021-libcc1-fix-vector-include.patch - patches-13.x/400-LoongArch-Fix-MUSL_DYNAMIC_LINKER.patch - patches-13.x/401-LoongArch-Modify-MUSL_DYNAMIC_LINKER.patch Refresh patches: - patches-13.x/300-mips_Os_cpu_rtx_cost_model.patch - patches-13.x/970-macos_arm64-building-fix.patch Signed-off-by: Olcay Korkmaz

toolchain: gcc: add support for GCC 14

2024-05-12T11:47:12Z

Deleted (upstreamed): - 020-Include-safe-ctype.h-after-C-standard-headers-to-avo.patch [1] - 021-libcc1-fix-vector-include.patch [2] All other patches automatically rebased. Note that selecting GCC 14, as of now, *will* result in build failures. The packages that fail to build will be fixed as they're found. Thus, GCC 13.x is the default, for the time being. [1] https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=9970b576b7e4ae337af1268395ff221348c4b34a [2] https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=5213047b1d50af63dfabb5e5649821a6cb157e33 Signed-off-by: Rui Salvaterra

toolchain/gcc: fix loongarch64 ldso file name

2024-05-04T06:12:56Z

GCC has changed musl dynamic linker name from ld-musl-loongarch-lp64d.so.1 to ld-musl-loongarch64.so.1 recently [1]. Meanwhile musl 1.2.5 only supports the new name. So it's better to follow the new name. [1] https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=8bccee51f0deac64b79cd9ad75df599422f4c8ff Signed-off-by: Weijie Gao

config: fix CONFIG_GDB appearing in main menuconfig menu

2024-04-09T17:30:41Z

I noticed that CONFIG_GDB was suddenly appearing in the main menuconfig menu despite the fact that it should be visible only when TOOLCHAINOPTS is selected and under a dedicated menu. After some trial and error, it seems that this was caused by the recent addition of GCC_USE_DEFAULT_VERSION, and after even more trial and error it gets fixed as soon GCC_USE_DEFAULT_VERSION is placed after GCC_VERSION. So, lets simply put GCC_USE_DEFAULT_VERSION after GCC_VERSION. Fixes: 501ef81040ba ("config: select KERNEL_WERROR if building with default GCC version") Signed-off-by: Robert Marko

config: select KERNEL_WERROR if building with default GCC version

2024-04-08T00:40:15Z

At the moment we have to manually follow the default GCC version also in config/Config-kernel.in. This tends to be forgotten at GCC version bumps (just happened when switching from version 12 to 13). Instead, introduce a hidden Kconfig symbol which implies KERNEL_WERROR in toolchain/gcc/Config.in where it is visible for developers changing the default version. Also remove the explicit default on BUILDBOT to avoid a circular dependency and also because buildbots anyway implicitly always select the default GCC version. Reference: https://github.com/openwrt/openwrt/pull/15064 Signed-off-by: Daniel Golle

toolchain/gcc: fix build errors on macOS with Xcode 15.3

2024-04-02T09:10:32Z

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1/__locale:550:5: error: '__abi_tag__' attribute only applies to structs, variables, functions, and namespaces _LIBCPP_INLINE_VISIBILITY ^ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1/__config:891:37: note: expanded from macro '_LIBCPP_INLINE_VISIBILITY' # define _LIBCPP_INLINE_VISIBILITY _LIBCPP_HIDE_FROM_ABI ^ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1/__config:870:26: note: expanded from macro '_LIBCPP_HIDE_FROM_ABI' __attribute__((__abi_tag__(_LIBCPP_TOSTRING(_LIBCPP_ODR_SIGNATURE)))) Fixed using backport of upstream commits [1-2] as discussed here https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632#c21 [1] Include safe-ctype.h after C++ standard headers, to avoid over-poisoning https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=9970b576b7e4ae337af1268395ff221348c4b34a [2] libcc1: fix include https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=5213047b1d50af63dfabb5e5649821a6cb157e33 Signed-off-by: Georgi Valkov

toolchain: gcc: switch default to 13

2024-03-23T22:47:29Z

Use GCC 13 instead of GCC 12 by default. All target kernels are building with GCC 13. Most packages from the feed are building fine. The root file systems is getting a little bit smaller for MIPS 32 BE and aarch64. With GCC 12 I got these sizes for lantiq/xrx200: 7,005,867 openwrt-lantiq-xrx200-tplink_tdw8970-initramfs-kernel.bin With GCC 13 I got these sizes for lantiq/xrx200: 6,989,754 openwrt-lantiq-xrx200-tplink_tdw8970-initramfs-kernel.bin With GCC 12 I got these sizes for armsr/armv8: 13,083,836 openwrt-armsr-armv8-generic-ext4-combined.img.gz 4,900,240 openwrt-armsr-armv8-generic-ext4-rootfs.img.gz 20,142,592 openwrt-armsr-armv8-generic-kernel.bin With GCC 13 I got these sizes for armsr/armv8: 13,068,966 openwrt-armsr-armv8-generic-ext4-combined.img.gz 4,893,078 openwrt-armsr-armv8-generic-ext4-rootfs.img.gz 20,142,592 openwrt-armsr-armv8-generic-kernel.bin Signed-off-by: Nick Hainke Signed-off-by: Hauke Mehrtens

scripts/ext-toolchain: implement external GCC version detection

2023-10-20T14:13:31Z

Some package may needs to enable compatibility option based on the GCC version. Currently the GCC version is set based on the default value and doesn't actually reflect the real value provided by the external toolchain if used. Fix this by correctly detecting the GCC version in the external toolchain and set the correct value in CONFIG_GCC_VERSION. A new option is added in menuconfig to manually set the GCC version if needed. Signed-off-by: Christian Marangi

toolchain: assign PKG_CPE_ID

2023-09-19T18:22:59Z

The PKG_CPE_ID links to NIST CPE version 2.2. Assign PKG_CPE_ID to all remaining package which have a CPE ID. Not every package has a CPE id. Related: https://github.com/openwrt/packages/issues/8534 Signed-off-by: Alexander Couzens

toolchain: gcc: updat to 13.2

2023-07-30T11:06:56Z

Release Notes: https://gcc.gnu.org/pipermail/gcc/2023-July/242148.html Remove upstreamed patches: - patches-13.x/001-rtl-optimization-109585-alias-analysis-typo.patch - patches-13.x/700-RISCV-Inline-subword-atomic-ops.patch - patches-13.x/701-riscv-linux-Don-t-add-latomic-with-pthread.patch Refresh patches: - patches-13.x/10-mbsd_multi.patch Signed-off-by: Nick Hainke