summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/gcc/gcc-11.2.inc
Commit message (Collapse)AuthorAgeFilesLines
* gcc: upgrade 11.2 -> current 12 snapshotuninative-3.6master-uninativeBernhard Rosenkränzer2022-04-091-123/+0
| | | | | | | | | | | | | | gcc 12 is expected to be released this month or early next month. Update so we're prepared. This keeps/ports all patches currently applied to 11.2 that haven't landed upstream yet. [v2: Back out the zephyr DWARF-4 workaround] (From OE-Core rev: 540116ca70fb71ac489b61b74b3a397ff92f27e2) Signed-off-by: Bernhard Rosenkränzer <bernhard.rosenkraenzer.ext@huawei.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: sanitizer: Fix tsan against glibc 2.34Sundeep KOKKONDA2022-04-031-0/+1
| | | | | | | | | | | | | | | 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/scripts: Automated conversion of OE renamed variablesRichard Purdie2022-02-211-1/+1
| | | | | | (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 : Fix CVE-2021-46195pgowda2022-02-121-0/+1
| | | | | | | | | 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-051-1/+0
| | | | | | | | | | | | | | | | | | | 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: Fix compile of gcc pluginsAndrei Gherzan2022-01-071-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: Fix CVE-2021-42574pgowda2021-12-171-0/+4
| | | | | | | | | | | | 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: Drop further unneeded precompiled header patchRichard Purdie2021-11-261-1/+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-261-1/+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-251-1/+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>
* gcc: Fix CVE-2021-35465Pgowda2021-11-161-0/+4
| | | | | | | | | | | | | | 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: Drop libgfortran patchRichard Purdie2021-10-301-1/+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: Drop testsuite failure fix patchRichard Purdie2021-10-291-1/+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-291-1/+1
| | | | | | | | | | | | | | | | | | | 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>
* gcc: Drop broken/unneeded patchRichard Purdie2021-10-261-1/+0
| | | | | | | | | | | | This patch looks obsolete because it looks like part of an upstream backport on a very old gcc version (4.3.3) and looks incomplete. The diff also has little context making it likely to be a rebase error. Builds seem find without it so drop it. (From OE-Core rev: 7bc50b6de2df8555f7e19ff37f103bbe65955f72) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Drop sdt (dtrace) header patchRichard Purdie2021-10-261-1/+0
| | | | | | | | | | Since we now have recipe specific sysroots we no longer need this patch to avoid the dtrace headers affecting the build of gcc-runtime. Drop the patch. (From OE-Core rev: 9aa8ff2dbbbf38cb0c87efd32db64b8ddf485ddf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Merge three related patches togetherRichard Purdie2021-10-261-2/+0
| | | | | | | | | The SYSTEMLIBS_DIR change was spread over three patches, merge these together since there is no value in having them separate. (From OE-Core rev: dd1fef1b520efaac6a21f26332c25bdcc0110c12) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Backport patch to make LTO builds more reproducibleTony Battersby2021-08-051-0/+1
| | | | | | | | | | | | Backport ustream gcc patch that enables -fdebug-prefix-map to cover additional cases with LTO enabled to make LTO builds more reproducible. [YOCTO #14481] (From OE-Core rev: 8923253b9bc91b14b474abc4923ca916fb8a12ec) Signed-off-by: Tony Battersby <tonyb@cybernetics.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: update 11.1 -> 11.2Bernhard Rosenkränzer2021-08-021-0/+118
Update gcc, drop patches that have been merged upstream (From OE-Core rev: 8979de58dc49fb4f8bc55743a1a4bf613c675a4e) Signed-off-by: Bernhard Rosenkränzer <bero@lindev.ch> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-09 10:42:26 +0000