summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/gcc
Commit message (Collapse)AuthorAgeFilesLines
* 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>
* gcc: Drop broken/unneeded patchRichard Purdie2021-10-262-71/+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-262-111/+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-264-77/+28
| | | | | | | | | 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: also relocate the musl loaderRoss Burton2021-08-221-0/+8
| | | | | | | | | Alongside GLIBC and UCLIBC, also relocate the musl loader. (From OE-Core rev: 24c4e01892df1510e5ba64b89a0060f62f2384e6) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Fix nativesdk builds and multilib fixes with gcc 11Richard Purdie2021-08-221-9/+15
| | | | | | | | | | | | | | In newer gcc versions the headers changed locations and our multiconfig and nativesdk tweaks to loader paths wasn't working. The broke buildtools-extended-tarball, particularly on arm. Update to fix this. Ultimately we should dump the gcc specs and check for hardcoded paths. This isn't possible quite yet as this patch doesn't fix the musl ones as we don't use that in mutlilib or nativesdk scenarios at present. (From OE-Core rev: 4ed6505a18ac76c0aa148deabb143214ac0c4552) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Backport patch to make LTO builds more reproducibleTony Battersby2021-08-052-0/+96
| | | | | | | | | | | | 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>
* meta: convert nested overrides leftovers to new syntaxDenys Dmytriyenko2021-08-043-6/+6
| | | | | | | | | Those were missed in previous rounds of automated and manual conversion. (From OE-Core rev: 22f9c7268b542baf6cd8aa0e34c8fb7aa1579e08) Signed-off-by: Denys Dmytriyenko <denis@denix.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: update 11.1 -> 11.2Bernhard Rosenkränzer2021-08-0215-588/+3
| | | | | | | | | 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>
* Convert to new override syntaxRichard Purdie2021-08-0217-182/+182
| | | | | | | | | | | | This is the result of automated script conversion: scripts/contrib/convert-overrides.py <oe-core directory> converting the metadata to use ":" as the override character instead of "_". (From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Apply multilib fix to ARC as wellAlexey Brodkin2021-06-221-3/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* gcc: replace gdb helper install revert with the upstream fixRoss Burton2021-06-173-77/+58
| | | | | | | | | | | 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>
* Revert "libgcc-initial: Do not build fp128 to decimal ppc functions"Khem Raj2021-06-171-2/+0
| | | | | | | | | | | | | | This is now fixed in gcc properly, and the patches are backported into gcc11 branch which OE updated to recently. https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=645bfc161987a12395869728b63ed01084d23c00 https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=f1d012911bd103e9701ed378f32928a3cbcf028a This reverts commit 7883b4c1384fe30066072f39e9a930be537bc3b4. (From OE-Core rev: ab8b8153469a038b09b6ff24be41f5942dca60ab) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Fixes for ARCAlexey Brodkin2021-06-124-0/+525
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* gcc: enable branch protection by standardRoss Burton2021-06-081-0/+1
| | | | | | | | | | | | | | | | Pass --enable-standard-branch-protection. This is an aarch64-specific option (currently) which does nothing on other targets. On aarch64 this generates code uses BTI/PAC instructions to mitigate Return Orientated Programming attacks. This approach is backwards compatible and the code size/performance impact is typically negliable. More details can be found at https://events.static.linuxfound.org/sites/events/files/slides/slides_23.pdf (From OE-Core rev: 84e6064cde02b463066d7b63fcf8baf392491327) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: revert libstc++-gdb.py installation changesRoss Burton2021-05-272-0/+77
| | | | | | | | | | | | | | | 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>
* gcc: Update to latest on release/gcc-11 branchKhem Raj2021-05-251-2/+6
| | | | | | | | | | | | There has been 150+ fixes made available after gcc 11.1.0 was released, details of these fixes is here https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff_plain;hp=releases/gcc-11.1.0;h=9ee61d2b51d (From OE-Core rev: 3dae2c37d68ba25266934156fced0eb85e1dcd8a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: add symlinks for ld.bfd and ld.goldSamuli Piippo2021-05-251-1/+1
| | | | | | | | | | | | When -fuse-ld gcc option is used, missing ld.bfd or ld.gold symlinks can lead to linker error: collect2: fatal error: cannot find 'ld' (From OE-Core rev: 9ec1cd0a1e4cc2740be37585231279adf91c47d7) Signed-off-by: Samuli Piippo <samuli.piippo@qt.io> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Refresh patch to fix patch fuzzKhem Raj2021-05-181-8/+2
| | | | | | | | | | | | | | | | | | 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>
* gcc: Extend .gccrelocprefix section support to musl configsKhem Raj2021-05-181-9/+170
| | | | | | | | | | | 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>
* gcc: Add target gcc include search for musl config tooKhem Raj2021-05-181-4/+60
| | | | | | | | | | | | | | 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>
* gcc-sanitizers: Package up static hwasan files as wellMartin Jansa2021-05-111-1/+3
| | | | | | | | | | | * introduced with gcc-11, other hwasan files were already packaged in: 3df4a25465 gcc-sanitizers: Package up hwasan files but static library was still triggering installed-vs-shipped (From OE-Core rev: 49aec04aa8ac98545b48c41382ebf1a1c3be1118) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to GCC 11Khem Raj2021-05-0349-427/+222
| | | | | | | | | 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>
* libgcc-initial: Do not build fp128 to decimal ppc functionsKhem Raj2021-05-031-0/+2
| | | | | | | | | | | | | | | These functions depend on glibc headers e.g. stdlib.h/fenv.h/string.h/stdio.h which do not exist when building lbgcc-initial, and these functions are not needed during glibc build so we are fine to disable them introdcued with [1] [1] https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=781183595acba67a37c66f59a0c1d9b5fee7e248 (From OE-Core rev: 7883b4c1384fe30066072f39e9a930be537bc3b4) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: Fix __FILE__ related reproducablity issuesKhem Raj2021-05-011-0/+1
| | | | | | | | | | | | | | | | | libstdc++ uses assertion macros which use __FILE__ macros and if (__builtin_expect(!bool(_Condition), false)) \ std::__replacement_assert(__FILE__, __LINE__, __PRETTY_FUNCTION__, \ #_Condition) This ends up using absolute paths into build tree for the cases where the charconv header is used, therefore replace the file prefix paths with on-target paths to make them build dir independent (From OE-Core rev: 972c50d6e46ee9dfba8b8ea3867ebdbf24001e6e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: Install LTO linker plugin to BFD searchable locationKhem Raj2021-04-271-1/+8
| | | | | | | | | | This helps binutils provided tools ar/ranlib/nm to find the LTO linker plugin automatically as well which makes it equivalent to gcc-ar/gcc-nm/gcc-ranlib (From OE-Core rev: 7d8d0b90bea7ea01e1e9ab0ff98f22431f68a506) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross: Install linker LTO plugin for binutils toolsKhem Raj2021-04-271-1/+7
| | | | | | | | | | | | This will ensure that ar/ranlib/nm can load the lto linker plugin like gcc-ar, gcc-nm, gcc-ranlib does, this will let the behaviour match between gcc wrappers for these tools, this should help LTO builds for packages (From OE-Core rev: d6658505089234476c1b35fc08fef1eb4f121e85) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-target: Create a LTO plugin symlink in bfd-plugins directoryKhem Raj2021-04-271-1/+3
| | | | | | | | | | | | | | | | This directory is scanned by binutils provided ar,ranlib,nm for plugins that it can load automatically, putting liblto_plugin.so in their means we do not need gcc-ar, gcc-nm, gcc-ranlib particularly as normal ar/ranlib/nm tools will work equally well as they can now use this linker plugin by default This also mean we can revert back to using ar/ranlib/nm as default providers for AR/NM/RANLIB on target (From OE-Core rev: 5aae5812223792d5e5bd57e024de50fbcd1e6da5) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: Make DEBUG_PREFIX_MAP relative to SKhem Raj2021-04-181-6/+7
| | | | | | | | | | | | | | | | Current definition of SLIB is actually equal to S but is hardcoded, this means when we have altered location of S, then the regexp for DEBUG_PREFIX_MAP will not be effective, which could result in S being emitted into debug_line sections. Simplify the maps to use S variable instead of SLIB Secondly, rename SLIB_NEW to REL_S to make it more appropritate to what it represents (From OE-Core rev: 2c8e130adb5d4d55ba732a042ec157498460ee29) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to 10.3.0 bug-fix releaseKhem Raj2021-04-1853-1680/+139
| | | | | | | | | | | | 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>
* gcc-sanitizers: Package up hwasan filesKhem Raj2021-03-201-1/+2
| | | | | | | | | This is introduced in GCC-11 (From OE-Core rev: 3df4a25465e488ba7c17d0b358435fc1088c6dac) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Update patch to only patch files onceWang Mingyu2021-03-201-62/+43
| | | | | | | | | | | | 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>
* gcc: Package new module mapper toolKhem Raj2021-03-141-0/+1
| | | | | | | | | | | This is new tool in GCC 11 [1] [1] https://gcc.gnu.org/onlinedocs/gcc/C_002b_002b-Module-Mapper.html (From OE-Core rev: 91e1b8f84471fda3d5173a5ab2fe9458f9233007) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross: make use of the system include directories fatalRoss Burton2021-03-101-1/+1
| | | | | | | | | | When building the cross GCC, configure it so that including the host system include directories is fatal, not just a warning. (From OE-Core rev: d039d6fbfc9076f081173f6e5cc63c56fe3a5adb) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: add an option for --enable-poison-system-directories to be fatalRoss Burton2021-03-101-3/+53
| | | | | | | | | | 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>
* gcc-sanitizers: Move content from gcclibdir into libdirMike Crowe2021-03-021-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In e9e5744ba8b0d43c8b874d365f83071ce20bf0a1, Khem Raj wrote: > OE does not use the traditional /usr/lib/gcc prefix to store > gcc-runtime it basically is moved into libdir, however some newer > files were installed by newer versions of gcc especially libgomp ( > omp.h openacc.h ) into gcclibdir, so we have content in both > directories, this confuses other tools which are trying to guess the > gcc installation and its runtime location, since now we have two > directories, the tools either choose one or other and we get > inconsistent behavior, e.g. clang for aarch64 uses /usr/lib but same > clang for riscv64 chose /usr/lib/gcc > This change ensures that OE ends up with single valid location for gcc > runtime files I think that the same thing needs to happen in gcc-sanitizers.inc, otherwise I get errors like: | .../recipe-sysroot/usr/include/gpg-error-64.h:884:11: fatal error: sanitizer/lsan_interface.h: No such file or directory when attempting to compile with sanitizers enabled. FILES_${PN} needs updating to match too. (From OE-Core rev: 862b4fac3ee7d951758c8c93462331ad52bf0190) Signed-off-by: Mike Crowe <mac@mcrowe.com> Cc: Khem Raj <raj.khem@gmail.com> Cc: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/recipes-devtools: Add HOMEPAGE / DESCRIPTIONDorinda2021-02-261-0/+1
| | | | | | | | | | | Added HOMEPAGE and DESCRIPTION for recipes with missing decriptions or homepage [YOCTO #13471] (From OE-Core rev: bb05814335e7101bfd8df0a11dc18a044e867bed) Signed-off-by: Dorinda Bassey <dorindabassey@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Backport patch to resolve i*86 tune configuration overridesNathan Rossi2021-01-203-114/+209
| | | | | | | | | | | 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>
* gcc: Add patch to resolve i*86 tune configuration overridesNathan Rossi2020-12-182-0/+114
| | | | | | | | | | | | | | | | | | | | 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>
* gcc: Handle duplicate names for variablesKhem Raj2020-11-111-5/+8
| | | | | | | | | | 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>
* gcc: Do no parameterize LTO configuration flagsKhem Raj2020-11-111-2/+1
| | | | | | | | | | | These flags are redundant as LTO now enabled in GCC by default for sometime, Moreover, dropping LTO variable here avoids a conflict with global LTO variable being added for distrowide LTO support (From OE-Core rev: 50cd8edc9849d6ab6249d4c49c7e41bb476dcb71) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-11 11:20:49 +0000