summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/gcc
Commit message (Collapse)AuthorAgeFilesLines
...
* gcc-multilib-config: Fix i686 toolchain relocation issuesRichard Purdie2022-09-031-1/+1
| | | | | | | | | | | | | This code wasn't changing the linux.h on i686. Make the entry match that for i586 which was correct. This fixes problems where the wrong dynamic loader path was used by nativesdk-gcc on i686 SDK targets by ensuring SYSTEMLIBS_DIR is replaced by %r in the correct header files. (From OE-Core rev: d30eb681f41bf9e921f7f0d42747fff7a4be9229) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to 12.2.0Khem Raj2022-08-2512-49/+3
| | | | | | | | | | | | | | | | | | GCC 12.2 is the first bug-fix release from the GCC 12 branch containing important fixes for regressions and serious bugs in GCC 12.1 with more than 71 bugs fixed since the previous release comprising of a number of libstdc++ and C++ and fortran fixes [1] Remove backported patch to fix libsanitizers with glibc 2.36, its already present in 12.2 [1] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=12.2 (From OE-Core rev: b73f5c0a7b94d9d04dd69fe5a5b871eab05714a3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Update patch status to submitted for two patchesRichard Purdie2022-08-172-2/+3
| | | | | | (From OE-Core rev: a2f52f6f698a1073f264dfb8afcdb4dcbcec6be8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Add a patch to avoid hardcoded paths in libgcc on powerpcRichard Purdie2022-08-172-0/+20
| | | | | | | | | Tweak the powerpc code to just include filenames rather than full paths to avoid build reproducibility issues. (From OE-Core rev: a71832a14b6944da10c1916861545577f2f2de2c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Resolve relative prefix-map filenamesRichard Purdie2022-08-172-0/+63
| | | | | | | | | | | | Add a patch to gcc so that relative paths are handled by -fdebug-prefix-map and friends. In OE we use relative paths in autotools and removing that creates a lot of issues we'd have to fix. This alternative allows us to fix the paths within gcc and improve our debug file coverage (and SPDX manifests) accordingly. (From OE-Core rev: 591cbe7140f01470b5799bc51e5b23f58bf95ffa) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross: Fix relative linksRichard Purdie2022-08-171-0/+1
| | | | | | | | | | Now that we're using absolute paths to run configure, there are absolute path symlinks within gcc's output. Use our script that fixes these so that the sstate objects work correctly. (From OE-Core rev: 78f0bb21ae4337fdf628b2436c6182c32ed4fa9d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Handle S and B separately for debug mappingRichard Purdie2022-08-172-21/+0
| | | | | | | | | | | | | | | | | We don't really need to keep S and B separate for debug source purposes and there shouldn't be source references in WORKDIR that isn't S and B either. Separating these out simplifies the shared-work directory handling for gcc and should also help fix external source usage. Therefore handle S and B in DEBUG_PREFIX_MAP separately and clean up other code. Indentation is reduced here as it is introduced on every compiler commandline so minimising it is helpful. (From OE-Core rev: c39b5020b8705d17e3745c41e38d0f99a1ac94cf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgcc/gcc-runtime: Improve source reference handlingRichard Purdie2022-08-172-14/+19
| | | | | | | | | | | | | | | | | | | | | | This code was some of the earliest reproducible build work we did. To correctly handle the encoding of file paths, we used relative build paths to run configure which resulted in relative build paths in the binaries. We now have more modern approaches used elsewhere with the prefix remapping options. These work best with absolute paths, not relative ones. As such, drop the relative path mangling and switch to using prefix mapping exclusively on absolute paths. This makes the code matc the rest of the system and triggers the correct code to be added in /usr/src/debug. We have to include both file-prefix and debug-prefix since the assembler only looks at debug-prefix. (From OE-Core rev: 309e5d8bb56eb8599d756831f0bd38e6a50cfb05) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-sanitizers: Fix mount.h glibc 2.36 conflictKhem Raj2022-08-022-0/+46
| | | | | | | | | | backport a sanitizers upstream patch (From OE-Core rev: ca1fef4cb33b5f218cd0206002e8776d2f68b12d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgcc: Fix standalone target builds with usrmerge distro featureKhem Raj2022-07-251-2/+6
| | | | | | | | | | | Ignore the rmdir cmd if using usrmerge distro feature since the intention is to delete /lib or /lib64 but not libdir under /usr and base_libdir = libdir when usrmerge is enabled in distro (From OE-Core rev: 3b7f6b0e0f1f16f89cd924aac001b4f661c145ca) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: Use static dummy libstdc++Khem Raj2022-07-251-1/+2
| | | | | | | | | | some standalone targets e.g. riscv64-elf disable shared linking for baremetal ELF ABI in ld, therefore lets make it a static library (From OE-Core rev: 3c6219dfcbcbde314648ba8cc54a90b32ea1c952) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: Use --with-target-subdir for baremetal targetsKhem Raj2022-07-251-1/+2
| | | | | | | | | | | | | | | | | This disables tests for runtime system specific functions like fcntl there is no other change seen +configure:77372: checking for fcntl +configure:77372: result: yes In libsttdc++ configure log outputs. [YOCTO #14803] (From OE-Core rev: 586b6239252ecf2711930b60f7f0f617e38ac737) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: Pass -nostartfiles when building dummy libstdc++.soKhem Raj2022-07-221-2/+1
| | | | | | | | | | | This is a dummy shared object therefore reduce dependencies further by not requiring the C startup files, we wont use this shared library for anything useful anyway (From OE-Core rev: e1c4953f5587621d4911416c2e9350ad0c27b296) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: Fix missing MLPREFIX in debug mappingsRichard Purdie2022-07-151-1/+1
| | | | | | | | | This fixes reproducibility issues with multilibs were a different recipe specific sysroot is used which was leaking into debug symbols in libraries. (From OE-Core rev: f442edf51e256bd315bd8e4ac4d9fa12b8e9e092) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: Fix build when using goldRichard Purdie2022-07-141-1/+2
| | | | | | | | | | | | | | | | If gold is enabled as the default linker, it errors trying to link to our dummy library empty file and this turns off things which should be present in libstdc++. For example, _GLIBCXX_HAVE_S_ISREG isn't defined and HAVE_S_ISREG in libstdc++-v3/config.h isn't set properly. Instead of just creating an empty file, create an empty elf binary instead which addresses the issue. (From OE-Core rev: 2070bcd10aa3a05c96c8501c6a8c1e129fb1d440) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Backport a fix for gcc bug 105039pgowda2022-07-142-0/+93
| | | | | | | | | | | | Backport a fix from: https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=9234cdca6ee88badfc00297e72f13dac4e540c79 which fixes rust recursion issues in the demangler. (From OE-Core rev: bd2c8ed2d3ddec21cfcc44b26feee0285e0cd441) Signed-off-by: pgowda <pgowda.cve@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/recipes: Introduce add DEV_PKG_DEPENDENCY to change ↵Richard Purdie2022-06-281-2/+2
| | | | | | | | | | | | RDEPENDS:${PN}-dev There is a pattern that several recipes need to break the dependency of ${PN}-dev on ${PN}, most often as ${PN} may be be empty. Add a new variable to parameterise this and allow it to be changed more easily. (From OE-Core rev: a5b381c0f45c590a762647a9956a8f41e2e2315e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-source: Fix incorrect task dependencies from ${B}Richard Purdie2022-06-152-1/+2
| | | | | | | | | | | | | | | | Some tasks may reference ${B} for gcc-source which in general would not exist. It has dependencies on HOST_SYS and TARGET_SYS which are not appropriate for a shared recipe like gcc-source. This causes problems for the archiver and multiconfigs in particlar. Set B to something else to avoid these task hash issues. Acked-by: Jose Quaresma <jose.quaresma@foundries.io> (From OE-Core rev: beb2a76c591e985c6fc7ed473abd1bee27f955a2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: Add nativesdk-zstd dependencyRichard Purdie2022-06-041-1/+1
| | | | | | | | | To match the changes to gcc-cross, add a nativesdk-zstd dependency to ensure our configurations match. (From OE-Core rev: c145e00710fe557b5a3832fdc556ad53434b3615) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: depend on zstd-nativeJeremy Puhlman2022-06-021-1/+1
| | | | | | | | | | | | | Sharing sstate cache binaries between two systems, one with libzstd installed and the other without, leads to various gcc components being linked against the system libzstd and failing to run on the system with out it installed. Make zstd-native from our system available. (From OE-Core rev: 2b0a6f03137f24b211c8881cebf65732e550a942) Signed-off-by: Jeremy A. Puhlman <jpuhlman@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: upgrade 11.3 -> 12.1Khem Raj2022-05-1048-5663/+532
| | | | | | | | | | | | | | | | Major gcc release with lot of changes [2] - Add patch to re-shuffle include of sched.h to fix build on musl - porting guide to gcc 12 [1] - Fix version in maintainers entry [1] https://gcc.gnu.org/gcc-12/porting_to.html [2] https://gcc.gnu.org/gcc-12/changes.html (From OE-Core rev: b8878cf0d35cf3d1ac30576d9b9943a7761c011b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to 11.3 releaseKhem Raj2022-04-2248-961/+371
| | | | | | | | | | | | | This is a bugfix release on gcc-11 series, fixes 189 bugs [1] Drop backported patches already included in 11.3 release [1] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=11.3 (From OE-Core rev: c6d508157058adae401059e36df7fa778852859b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: sanitizer: Fix tsan against glibc 2.34Sundeep KOKKONDA2022-04-032-0/+24
| | | | | | | | | | | | | | | The patch is needed in order to support recent glibc (2.34). libsanitizer/ChangeLog: PR sanitizer/101749 * sanitizer_common/sanitizer_posix_libcdep.cpp: Prevent generation of dependency on _cxa_guard for static initialization. (From OE-Core rev: c44c4e7fb3c860d9fcb2aada0c9d4acb1e1e8101) Signed-off-by: Sundeep KOKKONDA <sundeep.kokkonda@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta, meta-selftest: Replace more non-SPDX license identifiersPeter Kjellerstedt2022-03-011-1/+1
| | | | | | | | | | | | | | | | In commit ceda3238 (meta/meta-selftest/meta-skeleton: Update LICENSE variable to use SPDX license identifiers) all LICENSE variables were updated to only use SPDX license identifiers. This does the same for comments and other variables where it is appropriate to use the official SPDX license identifiers. There are still references to, e.g., "GPLv3", but they are then typically in descriptive text where they refer to the license in a generic sense. (From OE-Core rev: 165759dced7fbe73b1db2ede67047896071dc6d0) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/scripts: Automated conversion of OE renamed variablesRichard Purdie2022-02-212-2/+2
| | | | | | (From OE-Core rev: aa52af4518604b5bf13f3c5e885113bf868d6c81) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/meta-selftest/meta-skeleton: Update LICENSE variable to use SPDX ↵Richard Purdie2022-02-201-1/+1
| | | | | | | | | | | | | license identifiers An automated conversion using scripts/contrib/convert-spdx-licenses.py to convert to use the standard SPDX license identifiers. Two recipes in meta-selftest were not converted as they're that way specifically for testing. A change in linux-firmware was also skipped and may need a more manual tweak. (From OE-Core rev: ceda3238cdbf1beb216ae9ddb242470d5dfc25e0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-target: move cc1plus to g++ packageStefan Herbrechtsmeier2022-02-121-1/+0
| | | | | | | | | | Move cc1plus from gcc to g++ package. Therefor, remove the duplicate FILES entry from gcc package and keep the entry in g++ package. (From OE-Core rev: f16c0efdeaca7cd08bd5609141b1094139e746f9) Signed-off-by: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-target: fix glob to remove gcc-<version> binaryStefan Herbrechtsmeier2022-02-121-1/+1
| | | | | | | | | | The glob to remove the gcc-<version> binary expects a single-digit major version which is no longer true. (From OE-Core rev: 30de10cf939cf65c0cab6730a3575bced5c7533a) Signed-off-by: Stefan Herbrechtsmeier <stefan.herbrechtsmeier@weidmueller.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc : Fix CVE-2021-46195pgowda2022-02-122-0/+129
| | | | | | | | | Upstream-Status: Backport [https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=f10bec5ffa487ad3033ed5f38cfd0fc7d696deab] (From OE-Core rev: 81e9f8aedab70dfb0a016601150623ef9a7c1596) Signed-off-by: pgowda <pgowda.cve@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Drop stdlib++ option patchRichard Purdie2022-02-053-121/+6
| | | | | | | | | | | | | | | | | | | 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 <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: Fix cross canadian compiler for baremetal targetsAlejandro Hernandez Samaniego2022-01-121-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <stdint.h> ^~~~~~~~~~ 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 <alejandro@enedino.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Fix typo in linux64.h install patchAndrei Gherzan2022-01-111-1/+1
| | | | | | | | | | 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 <andrei.gherzan@huawei.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Fix compile of gcc pluginsAndrei Gherzan2022-01-072-0/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <andrei.gherzan@huawei.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Update status of musl stddef.h patchKhem Raj2021-12-211-1/+1
| | | | | | | | | This patch has been accepted upstream (From OE-Core rev: 4c644708798f258d45dbcfa01909626de32710d4) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Fix CVE-2021-42574pgowda2021-12-175-0/+4766
| | | | | | | | | | | | 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 <pgowda.cve@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Add CVE-2021-37322 to the list of CVEs to ignoreRichard Purdie2021-12-091-0/+3
| | | | | | | | The CVE applies to binutils 2.26 and not to gcc so ignore there. (From OE-Core rev: fea2726663a3db03170c49fceaffc632c509aeea) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Update patch status submitted->backportRichard Purdie2021-12-061-1/+2
| | | | | | | | Patch was merged to upstream gcc, update status. (From OE-Core rev: ece8f1471db443d4844d475af9c89d16ef3fbab3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Drop further unneeded precompiled header patchRichard Purdie2021-11-262-58/+0
| | | | | | | | | 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 <richard.purdie@linuxfoundation.org>
* gcc: Drop mips default ABI patchRichard Purdie2021-11-262-55/+0
| | | | | | | | | | | 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 <richard.purdie@linuxfoundation.org>
* gcc: Drop no longer needed patchRichard Purdie2021-11-252-36/+0
| | | | | | | | | | | | | This patch was mentioned upstream a long time ago: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47256 Changes from gcc 10 onward mean it is no longer needed as mentioned in the above bug report. Drop the patch. (From OE-Core rev: 6fca075a8d87d033359f81d476c8506df66ad53d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* patches: correct whitespace/spelling for Upstream-Status tagsAlexander Kanavin2021-11-211-1/+1
| | | | | | | (From OE-Core rev: c613ca14c35a5d1782c79a25b83875cbfa2b952b) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Tweak Upstream-Status formattingRichard Purdie2021-11-194-4/+4
| | | | | | (From OE-Core rev: f05cdcb428634086c12c1a087196bd16678eda80) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Fix CVE-2021-35465Pgowda2021-11-165-0/+588
| | | | | | | | | | | | | | source : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102035 Upstream-Status: Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=3929bca9ca95de9d35e82ae8828b188029e3eb70] Upstream-Status: Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=574e7950bd6b34e9e2cacce18c802b45505d1d0a] Upstream-Status: Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=30461cf8dba3d3adb15a125e4da48800eb2b9b8f] Upstream-Status: Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=809330ab8450261e05919b472783bf15e4b000f7] (From OE-Core rev: c8a1726feaf705683e80d85811ae482c6ebc3172) Signed-off-by: Pgowda <pgowda.cve@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-common.inc: Remove mirrors that are no longer availablePeter Kjellerstedt2021-11-111-5/+1
| | | | | | | | | Also switch to https for https://gcc.gnu.org/pub/gcc/releases/ (From OE-Core rev: 45670d96119c3a483e9571821b6d5e984c2e2f93) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-common.inc: Clean up the additions to MIRRORSPeter Kjellerstedt2021-11-111-5/+5
| | | | | | | | | | Since commit 044fb04d in bitbake (fetch2: Allow whitespace only mirror entries) there is no need to separate the entries in MIRRORS with "\n". (From OE-Core rev: 5374c45725ef5796a563c0665cde0fc05cecd856) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgfortran: Set GFORTRANRichard Purdie2021-11-011-0/+5
| | | | | | | | | | The libgfortran configure sets FC to be $GFORTRAN. We did used to patch that out but rather than carry a patch to gcc, just set GFORTRAN as needed. (From OE-Core rev: 4ec096a9ce8a49b631efc50e7d95ff653d4c4374) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Drop libgfortran patchRichard Purdie2021-10-302-44/+0
| | | | | | | | | | | | | | As far as I can see, when building libgfortran we don't set GFORTRAN so this patch does nothing any more. The fortran build and gcc recipes have changed massively since gcc 4.2.2 so I think this patch is simply obsolete. I did test building libgfortran with and without this patch and there was no difference, the correct fortran compiler is found. If it were an issue we should just set GFORTRAN correctly. Therefore drop the patch. (From OE-Core rev: bc5209aa5f07cea00416852532b90aba044defd5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Add missing patch Upstream-StatusRichard Purdie2021-10-291-0/+2
| | | | | | (From OE-Core rev: c884878f6c833b18a3a95b193f5de68df5bcea48) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Drop testsuite failure fix patchRichard Purdie2021-10-292-256/+0
| | | | | | | | | | | | | | | This patch has headers as if it were submitted upstream but I can't find any record of it. I did try tests with it removed, building the referenced testsuite files with -Werror and it all works just fine with no warnings or errors (tested on MACHINE=qemux86). I suspect this was fixed in gcc itself in other ways. As such I think this patch isn't needed and suggest we drop it. If there is a reason it is needed, please report along with an example of how to reproduce issues. (From OE-Core rev: d83e12da74b853ae33045e5c216c90c78a19f54d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Update patches submitted/merged upstreamRichard Purdie2021-10-298-295/+374
| | | | | | | | | | | | | | | | | | | I took 5 of our patches and submitted to upstream gcc. This highlighted that patches 0026 and 0018 should be merged together and some tweaks were made to try and make it acceptable to upstream. The other patches have their headers updated to match what was submitted. The libstdc++ option patch was also cleaned up ready for upstream as the documentation wasn't quite right. The CXXFLAGS_FOR_BUILD piece of 0026 is separated out into a new patch which can be submitted separately to upstream. Two of the patches have been merged, status updated accordinly. (From OE-Core rev: df9b8ec56ff29f14feb1fde6acbdf9c4667430cf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-12 23:17:55 +0000