summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/gcc/gcc
AgeCommit message (Collapse)Author
2022-04-03gcc: sanitizer: Fix tsan against glibc 2.34Sundeep KOKKONDA
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>
2022-02-12gcc : Fix CVE-2021-46195pgowda
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>
2022-02-05gcc: Drop stdlib++ option patchRichard Purdie
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>
2022-01-11gcc: Fix typo in linux64.h install patchAndrei Gherzan
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>
2022-01-07gcc: Fix compile of gcc pluginsAndrei Gherzan
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>
2021-12-21gcc: Update status of musl stddef.h patchKhem Raj
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>
2021-12-17gcc: Fix CVE-2021-42574pgowda
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>
2021-12-06gcc: Update patch status submitted->backportRichard Purdie
Patch was merged to upstream gcc, update status. (From OE-Core rev: ece8f1471db443d4844d475af9c89d16ef3fbab3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-26gcc: Drop further unneeded precompiled header patchRichard Purdie
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>
2021-11-26gcc: Drop mips default ABI patchRichard Purdie
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>
2021-11-25gcc: Drop no longer needed patchRichard Purdie
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>
2021-11-21patches: correct whitespace/spelling for Upstream-Status tagsAlexander Kanavin
(From OE-Core rev: c613ca14c35a5d1782c79a25b83875cbfa2b952b) Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-19gcc: Tweak Upstream-Status formattingRichard Purdie
(From OE-Core rev: f05cdcb428634086c12c1a087196bd16678eda80) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-16gcc: Fix CVE-2021-35465Pgowda
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>
2021-10-30gcc: Drop libgfortran patchRichard Purdie
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>
2021-10-29gcc: Add missing patch Upstream-StatusRichard Purdie
(From OE-Core rev: c884878f6c833b18a3a95b193f5de68df5bcea48) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-10-29gcc: Drop testsuite failure fix patchRichard Purdie
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>
2021-10-29gcc: Update patches submitted/merged upstreamRichard Purdie
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>
2021-10-26gcc: Drop broken/unneeded patchRichard Purdie
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>
2021-10-26gcc: Drop sdt (dtrace) header patchRichard Purdie
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>
2021-10-26gcc: Merge three related patches togetherRichard Purdie
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>
2021-08-05gcc: Backport patch to make LTO builds more reproducibleTony Battersby
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>
2021-08-02gcc: update 11.1 -> 11.2Bernhard Rosenkränzer
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>
2021-06-22gcc: Apply multilib fix to ARC as wellAlexey Brodkin
W/o that hack target GCC assume existence of per-mcpu folders, which are missing. In particular G++ failed to find "bits/c++config.h": ------------------>8------------------ root@hsdk:~# cat test.cc #include <cstdlib> int myfunc(void) { } root@hsdk:~# g++ -c test.cc -v Using built-in specs. COLLECT_GCC=g++ Target: arc-oe-linux Configured with: ../../../../../../work-shared/gcc-11.1.0-r0/gcc-11.1.0/configure --build=x86_64-linux --host=arc-oe-linux --target=arc-oe-linux --prefix=/usr --exec_prefix=/usr -x Thread model: posix Supported LTO compression algorithms: zlib gcc version 11.1.1 20210523 (GCC) COLLECT_GCC_OPTIONS='-c' '-v' '-shared-libgcc' '-mcpu=hs38_linux' /usr/libexec/gcc/arc-oe-linux/11.1.1/cc1plus -quiet -v -imultilib hs38_linux -D_GNU_SOURCE test.cc -quiet -dumpbase test.cc -dumpbase-ext .cc -mcpu=hs38_linux -version -o /tmp/ccs GNU C++17 (GCC) version 11.1.1 20210523 (arc-oe-linux) compiled by GNU C version 11.1.1 20210523, GMP version 6.2.1, MPFR version 4.1.0, MPC version 1.2.1, isl version none GGC heuristics: --param ggc-min-expand=99 --param ggc-min-heapsize=129242 ignoring nonexistent directory "/usr/lib/gcc/arc-oe-linux/11.1.1/../../../../include/c++/11.1.1/arc-oe-linux/hs38_linux" ignoring nonexistent directory "/usr/lib/arc-oe-linux/11.1.1/include" ignoring nonexistent directory "/usr/local/include" ignoring nonexistent directory "/usr/lib/gcc/arc-oe-linux/11.1.1/../../../../arc-oe-linux/include" #include "..." search starts here: #include <...> search starts here: /usr/lib/gcc/arc-oe-linux/11.1.1/../../../../include/c++/11.1.1 /usr/lib/gcc/arc-oe-linux/11.1.1/../../../../include/c++/11.1.1/backward /usr/lib/gcc/arc-oe-linux/11.1.1/include /usr/lib/gcc/arc-oe-linux/11.1.1/include-fixed /usr/include End of search list. GNU C++17 (GCC) version 11.1.1 20210523 (arc-oe-linux) compiled by GNU C version 11.1.1 20210523, GMP version 6.2.1, MPFR version 4.1.0, MPC version 1.2.1, isl version none GGC heuristics: --param ggc-min-expand=99 --param ggc-min-heapsize=129242 Compiler executable checksum: 6df2f07a822bfbbb80a61414b712b75d In file included from test.cc:1: /usr/include/c++/11.1.1/cstdlib:41:10: fatal error: bits/c++config.h: No such file or directory 41 | #include <bits/c++config.h> | ^~~~~~~~~~~~~~~~~~ compilation terminated. ------------------>8------------------ Note "ignoring nonexistent directory "/usr/lib/gcc/arc-oe-linux/11.1.1/../../../../include/c++/11.1.1/arc-oe-linux/hs38_linux" message which is being used by GCC due to the fact of implicit "-mcpu=hs38_linux". In fact this header "bits/c++config.h" is located in "/usr/lib/gcc/arc-oe-linux/11.1.1/../../../../include/c++/11.1.1/arc-oe-linux" on target. (From OE-Core rev: fbdc4422361a520af458468d836a8e4159dc22d6) Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-06-17gcc: replace gdb helper install revert with the upstream fixRoss Burton
A change in the gcc-11 branch broke installation of the GDB helper on bare-metal targets without a shared libstdc++.so. This now fixed upstream so replacce the revert with a backport of the patch. (From OE-Core rev: 5137ca0a295c3ab8d938d67ea292300bb2cbab93) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-06-12gcc: Fixes for ARCAlexey Brodkin
A couple of fixes to be a part of 11.2 whenever it happens 1. https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=0061fabeb9393c362601486105202cfe837a5a68 Fixes "harfbuzz" build, see https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/issues/382 for all the gory details. 2. https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=4186b7e93be73f8d68dc0fcc00a4cc8cc83e99a8 Fixes ext4 run-time issue: ------------------------->8--------------------------- Path: /bin/busybox CPU: 0 PID: 1 Comm: init Not tainted 5.13.0-rc2-dirty #23 Invalid Read @ 0x41c9e600 by insn @ __bio_try_merge_page+0x4e/0xfc ECR: 0x00050100 EFA: 0x41c9e600 ERET: 0x80159656 STAT: 0x80080202 [IE K ] BTA: 0x80159648 SP: 0x80821b88 FP: 0x00000008 BLK: bio_add_page+0x22/0x5c LPS: 0x801a6a94 LPE: 0x801a6a98 LPC: 0x00000000 r00: 0x80823300 r01: 0xbfb85e38 r02: 0x00002000 r03: 0x00000000 r04: 0x80821b9b r05: 0x80821bfc r06: 0x00000000 r07: 0x00000700 r08: 0x00000000 r09: 0xffffffff r10: 0x00000000 r11: 0x00000000 r12: 0x8080b300 Stack Trace: __bio_try_merge_page+0x4e/0xfc bio_add_page+0x22/0x5c do_mpage_readpage+0x534/0x65c mpage_readahead+0x30/0xdc read_pages+0x34/0x194 page_cache_ra_unbounded+0x56/0x154 filemap_fault+0x25a/0x5d8 __do_fault+0x94/0xe8 handle_mm_fault+0x4de/0xbd4 do_page_fault+0x108/0x21c ret_from_exception+0x0/0x8 ------------------------->8--------------------------- 3. https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=5a9b6a004f89fdd95b0470e1324dc4dee8c41d24 Precautious fix for rare corner cases which we don't wnat to really end-up in. (From OE-Core rev: 75110a9cc5e6840c65ed24bcca7d4cf1748ab67d) Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-05-27gcc: revert libstc++-gdb.py installation changesRoss Burton
Commit dbb87d in the GCC 11 branch was intended to make the installation of this Python module more robust, but for unknown reasons the library_name in libstdc++.la in baremetal builds (for example, Zephyr) is unset, so the module is just installed as "-gdb.py". This may be a GCC bug, or a bug in our build. Until that is resolved, revert the commit to fix the packaging. (From OE-Core rev: 61947fc024bf18b42547d2ea4cad90184132994d) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-05-18gcc: Refresh patch to fix patch fuzzKhem Raj
This is due to previous patches editing common files from this patch Fixes ERROR: gcc-source-11.1.0-11.1.0-r0 do_patch: Fuzz detected: Applying patch 0028-Add-ssp_nonshared-to-link-commandline-for-musl-targe.patch patching file gcc/config/linux.h Hunk #1 succeeded at 203 with fuzz 1 (offset 8 lines). patching file gcc/config/rs6000/linux.h patching file gcc/config/rs6000/linux64.h (From OE-Core rev: d8c3f3a1872a41cc4788ff3d9f42c13debedabd2) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-05-18gcc: Extend .gccrelocprefix section support to musl configsKhem Raj
musl includes were not using the relocatable prefix like glibc counterpart, this will mean that musl SDKs will behave better and find the headers in right install directories (From OE-Core rev: 8cb141306f13fa6e25c89c104af9ad0af431eb5d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-05-18gcc: Add target gcc include search for musl config tooKhem Raj
Musl has different search order and therefore injects it via INCLUDE_DEFAULTS and does not use the defaults from gcc/cppdefaults.h, this ensures that same fix is extended to musl configs too where it can search for compiler headers It will fix builds with musl where omp.h is not found because it is in gcc includes path on target ( not cross ) sysroot (From OE-Core rev: 3ff688ca02dcc4c0187d1ddc214ec0c74b4e73f1) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-05-03gcc: Upgrade to GCC 11Khem Raj
Drop already upstream/backported patches (From OE-Core rev: e64bf999a92aed3c6be38eae9e75ec9277638b95) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-04-18gcc: Upgrade to 10.3.0 bug-fix releaseKhem Raj
Drop aarch64 backports which are already upstream List of bugs fixed is [1] [1] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&list_id=298084&resolution=FIXED&target_milestone=10.3 (From OE-Core rev: 023806e0e0de2b0e814e6e38d78bf2faa9661f19) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-03-20gcc: Update patch to only patch files onceWang Mingyu
This fixes an error in do_patch when using "PATCHTOOL = "patch"" error message: checking file gcc/configure.ac Hunk #1 FAILED at 6602. (From OE-Core rev: f75a1eddc7c01d9a83d0a1114fc0d6aaa79d8806) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-03-10gcc: add an option for --enable-poison-system-directories to be fatalRoss Burton
Extend --enable-poison-system-directories so that it can be an error instead of a warning by default. (From OE-Core rev: 1fcaa5f452b2c6b93a6f3dfd57f894cbef5e3379) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-01-20gcc: Backport patch to resolve i*86 tune configuration overridesNathan Rossi
Upstream has merged a change to handle detection of target overrides so that they are only applied as required. Backport this patch from upstream and remove the OE specific patch. (From OE-Core rev: d430f425e1a5725e93833a652e5c6988576f7347) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-12-18gcc: Add patch to resolve i*86 tune configuration overridesNathan Rossi
When compiling gcc-runtime for i686 libatomic, libgomp and libitm are compiled with additional '-march' and '-mtune' overrides. This typically does not cause build errors (e.g. core2-32 tune), and results in less optimally tuned outputs. However with specific TUNE_CCARGS (e.g. has '-mfpmath=sse' but not '-msse*'), the build errors with conflicting '-mfpmath' options. This is caused by gcc-runtime specific configure scripts and Makefile options that override by adding additional '-march'/'-mtune' args. OE builds gcc-runtime differently to other build systems, and provides target specific arch/tune options directly. As such, this change adds a patch for gcc to remove the specific cases where the args are added. (From OE-Core rev: d39b686cc5fcc89405ffeb560ea64b5d305b0608) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-11-11gcc: Handle duplicate names for variablesKhem Raj
PREFIXVAR is defined in cppdefaults.c as well which shows up as error when LTO is enabled to build gcc, therefore rename the one instance to PREFIXVAR1 (From OE-Core rev: 984da023a595a10ae62d4fc2a1f2fe96c4701223) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-08-18gcc: Upgrade to 10.2.0Khem Raj
Drop 0036-Enable-CET-in-cross-compiler-if-possible.patch and pr96130.patch they are already in 10.2 (From OE-Core rev: 35eda14fbdc38ae5e686c2d30a2c1d5569bd3088) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-06-03 06:55:36 +0000