linux/poky.git/meta/recipes-devtools/gcc, branch hardknott-next

gcc-sanitizers: Package up hwasan files

2021-03-20T18:54:56+00:00

This is introduced in GCC-11 (From OE-Core rev: 3df4a25465e488ba7c17d0b358435fc1088c6dac) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

gcc: Update patch to only patch files once

2021-03-20T18:54:56+00:00

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 Signed-off-by: Richard Purdie

gcc: Package new module mapper tool

2021-03-14T16:33:59+00:00

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 Signed-off-by: Richard Purdie

gcc-cross: make use of the system include directories fatal

2021-03-10T10:30:39+00:00

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 Signed-off-by: Richard Purdie

gcc: add an option for --enable-poison-system-directories to be fatal

2021-03-10T10:30:39+00:00

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 Signed-off-by: Richard Purdie

gcc-sanitizers: Move content from gcclibdir into libdir

2021-03-02T14:15:34+00:00

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 Cc: Khem Raj Cc: Alexandre Belloni Signed-off-by: Richard Purdie

meta/recipes-devtools: Add HOMEPAGE / DESCRIPTION

2021-02-26T15:21:21+00:00

Added HOMEPAGE and DESCRIPTION for recipes with missing decriptions or homepage [YOCTO #13471] (From OE-Core rev: bb05814335e7101bfd8df0a11dc18a044e867bed) Signed-off-by: Dorinda Bassey Signed-off-by: Richard Purdie

gcc: Backport patch to resolve i*86 tune configuration overrides

2021-01-20T00:45:05+00:00

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 Signed-off-by: Richard Purdie

gcc: Add patch to resolve i*86 tune configuration overrides

2020-12-18T22:52:24+00:00

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 Signed-off-by: Richard Purdie

gcc: Handle duplicate names for variables

2020-11-11T10:08:12+00:00

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 Signed-off-by: Richard Purdie