summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/gcc
Commit message (Collapse)AuthorAgeFilesLines
...
* 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>
* gcc10: Don't default back to -fcommonJacob Kroon2020-08-261-1/+0
| | | | | | | | | | | | It has been almost 3 months since the upgrade to gcc 10. Switch back to relying on gcc default configuration (-fno-common). This reverts OE-Core commit 951e859b1e8297970278c539e989b8a6d06a9cb3. (From OE-Core rev: 4ee733e1551d3960a23a600eb71a01cf7a51fa06) Signed-off-by: Jacob Kroon <jacob.kroon@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: Install gcc/g++ wrappers for muslKhem Raj2020-08-221-0/+23
| | | | | | | | | | | | | | gcc needs -mmusl option to be passed in SDK since we ship crossdk compiler configured for glibc by default, this helps in creating correct compiler defaults for musl based SDK compilers [YOCTO #13459] (From OE-Core rev: e6fbac7aeabe00d8fb734992012dd629a8527b25) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Leon Woestenberg <leon@sidebranch.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: Correct the regexp to delete versioned gcc binaryKhem Raj2020-08-211-1/+1
| | | | | | | | | | After gcc 10 this expression needed to be adjusted, its better to use a bitbake variable which we do have readily available (From OE-Core rev: ee2beaff701d02736c8244ebc76f6d6ca96a04f4) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to 10.2.0Khem Raj2020-08-1854-264/+6
| | | | | | | | | | 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>
* gcc-runtime.inc: fix m32 compile fail with x86-64 compilerChangqing Li2020-08-151-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | configuration: MACHINE ??= "qemux86-64" require conf/multilib.conf MULTILIBS ?= "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 ?= "core2-32" IMAGE_INSTALL_append = " packagegroup-core-buildessential lib32-libstdc++ lib32-libstdc++-dev" m32 compile failed on target: cmd: gcc -m32 -v test.cpp -o test output: GGC heuristics: --param ggc-min-expand=45 --param ggc-min-heapsize=29590 ignoring nonexistent directory "/usr/lib64/gcc/x86_64-poky-linux/10.1.0/../../../../include/c++/10.1.0/x86_64-poky-linux/32" ignoring nonexistent directory "/usr/lib64/x86_64-poky-linux/10.1.0/include" ignoring nonexistent directory "/usr/local/include" ignoring nonexistent directory "/usr/lib64/gcc/x86_64-poky-linux/10.1.0/../../../../x86_64-poky-linux/include" /usr/lib64/gcc/x86_64-poky-linux/10.1.0/../../../../include/c++/10.1.0 /usr/lib64/gcc/x86_64-poky-linux/10.1.0/../../../../include/c++/10.1.0/backward /usr/lib64/gcc/x86_64-poky-linux/10.1.0/include /usr/lib64/gcc/x86_64-poky-linux/10.1.0/include-fixed /usr/include End of search list. GNU C++14 (GCC) version 10.1.0 (x86_64-poky-linux) compiled by GNU C version 10.1.0, GMP version 6.2.0, MPFR version 4.1.0, MPC version 1.1.0, isl version none GGC heuristics: --param ggc-min-expand=45 --param ggc-min-heapsize=29590 Compiler executable checksum: bc3b2f3a33dad80e30112cf1235bf631 In file included from test.cpp:1: /usr/include/c++/10.1.0/iostream:38:10: fatal error: bits/c++config.h: No such file or directory 38 | #include <bits/c++config.h> | ^~~~~~~~~~~~~~~~~~ cannot find header since /usr/lib64/gcc/x86_64-poky-linux/10.1.0/x86_64-poky-linux/32 is missing fixed by link it to ../i686-poky-linux (From OE-Core rev: 509022ea8db314dd9d010a478fd84d0234905c6b) Signed-off-by: Changqing Li <changqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: backport a fix for out-of-line atomics on aarch64Ross Burton2020-08-122-0/+67
| | | | | | | (From OE-Core rev: ce99eb6b042cb36f5c07461fff7f49719550a955) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Fix mangled patchRichard Purdie2020-07-281-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To quote Zhuang <qiuguang.zqg@alibaba-inc.com>: """ A few days ago, I tried to compile a gcc plugin with the toolchain from poky sdk. It failed with errors about missing header files such as backend.h etc. After investigation, I found that the problem was brought by a gcc patch: 0012-gcc-Fix-argument-list-too-long-error.patch (which is considered derived from the original patch) - headers=`echo $(PLUGIN_HEADERS) $$(cd $(srcdir); echo *.h *.def) | tr ' ' '\012' | sort -u`; \ + headers="$(sort $(PLUGIN_HEADERS) $$(cd $(srcdir); echo *.h *.def))"; \ It changes the commands of install-plugin, making the sorting taken effect before the shell globs. Thus results in the header files under gcc $(srcdir) being not installed. By checking log.do_install, we can find that the `headers=' statement to run is incorrect and will not work as expected: headers="$(cd *.def) *.h ../../../../../../../work-shared/gcc-10.1.0-r0/gcc-10.1.0/gcc/../include/ansidecl.h ... As the patch says, "The PLUGIN_HEADERS is too long before sort, so the "echo" can't handle it, ..." my suggestion is that we can simply take care of PLUGIN_HEADERS using the original proposed sort. """ This fixes the gcc patch as proposed as it does appear its been broken over time. (From OE-Core rev: dce28d8ac7fbae487cb6674b91fe2b574036b26d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-10.1: add fix for PR 96130Dmitry Baryshkov2020-07-222-0/+107
| | | | | | | | | | Fix for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96130 causing ICE (SegFault) when compiling current Mesa git tree. (From OE-Core rev: bc2f2e72f20e6b272e48d1073bb2290665cbde24) Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: mitigate the Straight-line Speculation attackRoss Burton2020-07-224-0/+1470
| | | | | | | | | | | | | | | Straight-line Speculation is a SPECTRE-like attack on Armv8-A, further details can be found in the white paper here: https://developer.arm.com/support/arm-security-updates/speculative-processor-vulnerability/downloads/straight-line-speculation Backport the GCC patches to mitigate the attack. CVE: CVE-2020-13844 (From OE-Core rev: 3415e0ccdf75575014fb8c600edb707bbec0f566) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Remove mudflap remnantsAdrian Bunk2020-05-192-17/+0
| | | | | | | | | mudflap was removed in gcc 4.9. (From OE-Core rev: 6d649a07cfa0a89448caa67e4ca0a990973961b9) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Drop reverting __getauxval patchKhem Raj2020-05-153-50/+2
| | | | | | | | | Issue has been fixed in valgrind itself (From OE-Core rev: c4070f3d76e0170cf6ee672a8a9a38e4cdbbcad9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Do not set -march for arm64 for libatomicKhem Raj2020-05-153-4/+43
| | | | | | | | | | | | | | libatomic has mind of its own when it comes to setting -march for arm64 which conflicts with -mcpu option we pass from environment in some cases since we always pass -march/-mcpu in OE, its safe to remove this option mcpu removal from cortex-a55 is no longer needed since the option conflict is now removed from libatomic instead (From OE-Core rev: a5331c5a8bbe63c6c2e56ebec496b28968d4663d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc10: Revert using __getauxval in libgccKhem Raj2020-05-142-0/+48
| | | | | | | | | | This was added recently, but it seems be chewing more than what it should and causes non glibc packages also depend on it. (From OE-Core rev: 595d2df62b049e463568ab97cfe26d6df96a18a9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc10: Default back to -fcommonKhem Raj2020-05-141-0/+1
| | | | | | | | | | | For time being change back to -fcommon as default, helps us iron out other issues, eventually this should be removed as we fix the packages to work with -fno-common (From OE-Core rev: 951e859b1e8297970278c539e989b8a6d06a9cb3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc10: Update to GCC 10.1 ReleaseKhem Raj2020-05-1454-699/+492
| | | | | | | | | | | | | | | | | * Package new gomp header acc_prof.h * Package lto-dump which is a new tool in gcc10 * All Changes are here [1] * Porting apps to gcc 10 help is here [2] * Backport a patch to fix CET errors on cross builds * Add patch to fix mingw libstdc++ [1] https://gcc.gnu.org/gcc-10/changes.html [2] https://gcc.gnu.org/gcc-10/porting_to.html (From OE-Core rev: 44c3881b18f74eb64379818fc150f94398fb8a49) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: Avoid march conflicts with newer cortex-a55 CPUsKhem Raj2020-05-121-0/+4
| | | | | | | | | | | gcc-runtime/libatomic explicitly add -march=armv8-a+lse for all arch64 but cortex-a55 is armv8.2-a, which essentially conflicts, so let gcc override it by not forcing the -mcpu option from TUNE_CCARGS (From OE-Core rev: 882df891e13ce5c64718c364efb9ef2bf189eabf) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-target: Ensure buildtools-extended-tarball doesn't use arch=nativeRichard Purdie2020-05-021-5/+5
| | | | | | | | | | | | | | A nativesdk BBCLASSEXTEND was added to gcc-target without realising this would pass arch=native through to it for x86-64. This heavily optimises gcc output for the host its running on meaning it can't be reused via sstate on other machines. Add class-target overrides here to get the desired behaviour. All targets have been covered for completeness. (From OE-Core rev: d0d4853dd773f7bbe0f72e50144559b80e80d67a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Configure all gccs with --disable-install-libibertyKhem Raj2020-04-264-14/+1
| | | | | | | | | | | | | | | OE uses libiberty from binutils, since its properly compiled as pic archive and applications and other libraries needing libiberty can properly link with it. With this option applied, explicit delete of libiberty headers and libraries is not required in install step, since they wont get installed in first place. (From OE-Core rev: fa8a205c69770d23323c9a06373db958af4b34d3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-gcc-runtime: enable building libstdc++.aJeremy Puhlman2020-04-241-0/+2
| | | | | | | (From OE-Core rev: ef5cff3db22e911b7a6ecf3dac212903757b4df1) Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-runtime: apply ARM specific workaround to big-endian ARM tooAndre McCurdy2020-03-291-0/+1
| | | | | | | (From OE-Core rev: 633010f7c9f369565fd43465a857ad5680405e11) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-target: Use --with-arch=native for target gccKhem Raj2020-03-211-0/+1
| | | | | | | | | | | | | This should help gcc detect and use target ISA on x86_64 machines when -march is not used on cmdline [YOCTO #139] (From OE-Core rev: f9e410521c92e2458ba7e2ca63d28434618b9f25) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Upgrade to 9.3 bugfix releaseKhem Raj2020-03-1354-934/+230
| | | | | | | | | | | | This brings ~157 bugfixes [1] to gcc-9 with no features Drop backports which are already part of the release now [1] https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&list_id=260610&resolution=FIXED&target_milestone=9.3 (From OE-Core rev: caf80e4e245132bdc3bbe219b567013f2c5d2f46) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: strip line numbers from generated code in gcc-plugins on targetRoss Burton2020-03-112-0/+171
| | | | | | | | | The line numbers are influenced by the gcc version on the host used to generate the code. Remove these to ensure the shipped source code is the same. (From OE-Core rev: 5c3d3440809e9d76377af653ac8c5307bc1a01b4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-13 06:10:13 +0000