linux/poky.git/meta/recipes-devtools/gcc, branch uninative-3.5

gcc: Drop stdlib++ option patch

2022-02-05T12:26:35+00:00

The patch to gcc to disable use of libstdc++ when configuring the library during gcc-runtime is old and there are perhaps better ways to do this now. If removed, most builds still "work" but incorrect values for things like atomic ops are found during configure. mips64 and ppc fail with on target simple tests of g++ in testimage. Instead we can create a dummy libstdc++ which allows the correct configure test results to be obtained. Discussed with upstream about the patch are ongoing, if accepted, we can switch back to the commandline option if it is added in future. (From OE-Core rev: 34b0edb0d3120c32063ff7e3dd52be20d60401d5) Signed-off-by: Richard Purdie

gcc-cross-canadian: Fix cross canadian compiler for baremetal targets

2022-01-12T07:19:35+00:00

While building GCC it checks whether the include directory exists, if it doesnt it throws an error and exits: | The directory that should contain system headers does not exist: | tmp/work/x86_64-nativesdk-pokysdk-linux/gcc-cross-canadian-riscv32/ 11.2.0-r0/recipe-sysroot/usr/include/ | make[1]: *** [Makefile:3257: stmp-fixinc] Error 1 Even though for the baremetal toolchain not having this directory does make sense. We overcame this by removing the --with-sysroot=/not/exist argument for baremetal toolchains (via TARGET_OS override), however, the newlib toolchain does have headers and an includedir, hence by fixing the baremetal toolchain we broke the newlib one since it uses the same TARGET_OS as baremetal, causing for example (on newlib): /sdk/sysroots/x86_64-pokysdk-linux/usr/lib/riscv32-poky-elf/gcc/ riscv32-poky-elf/11.2.0/include/stdint.h:9:16: fatal error: stdint.h: No such file or directory | # include_next ^~~~~~~~~~ compilation terminated. By creating a dummy includedir, and removing the previous fix we allow GCC to be built the same way, unifying the cross compiler for all targets. After this fix both TCLIBC=baremetal and TCLIBC=newlib SDKs work properly. (From OE-Core rev: 08ff7c87efdf373f1874fcccd9a2a73fc0efef30) Signed-off-by: Alejandro Enedino Hernandez Samaniego Signed-off-by: Richard Purdie

gcc: Fix typo in linux64.h install patch

2022-01-11T15:48:10+00:00

The "gcc: Fix compile of gcc plugins" patch had a typo making it a noop. This was due to a rework to make it specific to the linux64.h header. (From OE-Core rev: 5f0f00f0988c02d7fe0fa62edf3e4901ce9941a6) Signed-off-by: Andrei Gherzan Signed-off-by: Richard Purdie

gcc: Fix compile of gcc plugins

2022-01-07T14:39:17+00:00

Without this, compiling gcc plugins will fail with an error similar to: [...] fatal error: ./config/i386/linux64.h: No such file or directory [...] In Yocto, we set up compiling gcc-cross out of tree. Which in turn makes the generated headers end up in B. The tm.h header will include generated headers that are expected in plugin/include/config/*. For example, the linux64.h header, when generating gcc-cross for x86-64, will end up in tm.h header as: include "./config/i386/linux64.h" On the other hand, the make rule `install-plugin` in gcc/Makefile.in will install the linux64.h assuming that it is generated in the sources directory and because this is not the case in our setup, the Makefile ends up installing it in plugin_includedir/`basename $$path` which ends up installing the header in [..]plugin/include as opposed to [..]plugin/include/config/i386 (as expected by the generator of tm.h). The included patch modifies the Makefile rule to match the assumption of gcc-cross being compiled out of tree. (From OE-Core rev: 92167f8e02bb6fbbe1ee6a6678525a0ae27b00a5) Signed-off-by: Andrei Gherzan Signed-off-by: Richard Purdie

gcc: Update status of musl stddef.h patch

2021-12-21T12:01:41+00:00

This patch has been accepted upstream (From OE-Core rev: 4c644708798f258d45dbcfa01909626de32710d4) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

gcc: Fix CVE-2021-42574

2021-12-17T09:56:14+00:00

Upstream-Status: Backport [https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=bd5e882cf6e0def3dd1bc106075d59a303fe0d1e] Upstream-Status: Backport [https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=51c500269bf53749b107807d84271385fad35628] Upstream-Status: Backport [https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=1a7f2c0774129750fdf73e9f1b78f0ce983c9ab3] Upstream-Status: Backport [https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=bef32d4a28595e933f24fef378cf052a30b674a7] (From OE-Core rev: 1276fa8b501aee1561b77538219d3cad2c796a21) Signed-off-by: pgowda Signed-off-by: Richard Purdie

gcc: Add CVE-2021-37322 to the list of CVEs to ignore

2021-12-09T10:33:25+00:00

The CVE applies to binutils 2.26 and not to gcc so ignore there. (From OE-Core rev: fea2726663a3db03170c49fceaffc632c509aeea) Signed-off-by: Richard Purdie

gcc: Update patch status submitted->backport

2021-12-06T11:21:52+00:00

Patch was merged to upstream gcc, update status. (From OE-Core rev: ece8f1471db443d4844d475af9c89d16ef3fbab3) Signed-off-by: Richard Purdie

gcc: Drop further unneeded precompiled header patch

2021-11-26T17:01:08+00:00

According to comments on the bug report from gcc developers, we no longer need to do this post gcc 10. Lets therefore drop the patch. (From OE-Core rev: 8ddc6f46d40cdcc462de23d1b1218f2ed9fd3d07) Signed-off-by: Richard Purdie

gcc: Drop mips default ABI patch

2021-11-26T17:01:08+00:00

gcc-configure-common.inc already sets --with-abi=64 for our mips64 targets so this patch is no longer needed. [YOCTO #14639] (From OE-Core rev: e0010af733825ed1050fd3342cf3ef1c478df1a0) Signed-off-by: Richard Purdie