staging/blogic/toolchain/gcc, branch master

toolchain: Don't force GCC8 on ARC

2019-07-07T11:02:05Z

This prevents overriding it to use GCC9. Signed-off-by: Rosen Penev Signed-off-by: Christian Lamparter [changed logic to not fall back on 7.4]

toolchain: Add GCC 9.1.0 release

2019-06-16T14:40:08Z

Most of the patches are copied over from GCC 8.3. The following patches are backported from the GCC 9.X development branch: toolchain/gcc/patches/9.1.0/970-recompute-dom-fast-queries-before-vn.patch toolchain/gcc/patches/9.1.0/975-g++-ICE-with-generic-lambda.patch The specs file changed with gcc 9, now it contains "%@{L*}" instead of "%{L*}" in older GCC versions. Signed-off-by: Joseph Benden

replace links towards lede-project.org with openwrt.org

2019-06-10T23:46:53Z

Modify VERSION_SUPPORT_URL VERSION_REPO Replace BUGS variable in toolchain/gcc/common.mk Signed-off-by: Alexander Couzens

toolchain: ARM: Fix option conflict with multiarch

2019-03-25T20:19:05Z

This problem exposed when compiling glibc, but applicable across the board. gcc compiles runtime libraries for all supported architectures, unless otherwise specified, and later selects applicable library based -m[arch,cpu,*] options, thus these options should not be passed to gcc as they break the compilation process. Signed-off-by: Boris Krasnovskiy Signed-off-by: Christian Lamparter [modified so it only touches ARM - I'm too chicken, changed authors email]

toolchain: ARM: Fix toolchain compilation for gcc 8.x

2019-03-25T20:15:58Z

Set the toolchain's ARM CPU and FPU architectures by utilizing' gcc's --with-cpu / --with-fpu configure options that: "Specify which cpu variant the compiler should generate code for by default. cpu will be used as the default value of the -mcpu= switch." This will resolve the following kernel compilation failures under gcc 8.x on ARM because the kernel wants to set (possibly conflicting) optimization flags. .../ccyVnmrs.s:204: Error: selected processor does not support `dmb ish' in ARM mode .../ccyVnmrs.s:215: Error: architectural extension `mp' is not allowed for the current base architecture .../ccyVnmrs.s:216: Error: selected processor does not support `pldw [r4]' in ARM mode Because this is a big change, the .config and toolchain need to be refreshed (as in removed and regenerated). Reported-by: Ansuel Smith Reported-by: Daniel Engberg [#1203] Signed-off-by: Boris Krasnovskiy Signed-off-by: Christian Lamparter [extended commit message, removed now-deprecated CPU_CFLAGS, changed author to gmail address]

toolchain: Remove GCC 7.1 for ARC targets

2019-03-20T17:23:39Z

Remove GCC 7.1 for ARC targets Signed-off-by: Daniel Engberg

toolchain: Use GCC 8.3.0 by default for ARC

2019-03-20T17:23:39Z

Use GCC 8.3.0 by default for ARC targets Includes a fix by Evgeniy Didin which fixes GCC version selection if DEVEL isn't set Signed-off-by: Daniel Engberg

toolchain: Update to GCC 8.3.0

2019-02-26T22:20:04Z

Update GCC to 8.3.0 Refresh patches Allow GCC to be used for ARC Source: https://github.com/openwrt/openwrt/pull/1803#issuecomment-462334890 Signed-off-by: Daniel Engberg

toolchain/gcc: Remove workaround for GCC 4.8

2019-02-26T22:20:04Z

GCC 4.8 was removed a long time ago... Signed-off-by: Daniel Engberg

toolchain/gcc: backport FORTIFY patch to 5.5.0

2019-02-04T08:35:11Z

Commit e61061a0886e2d0d6b075d75ae9b53d0a6bc9042 added support for hardening options in the toolchain. However this breaks the gcc5.5.0 compilation in case FORTIFY_SOURCE is set different from FORTIFY_SOURCE_NONE as reported in [1]. Fix this by backporting the upstream patch which fixes this in later gcc versions [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?format=multiple&id=61164 Signed-off-by: Hans Dedecker