toolchain/gcc: backport FORTIFY patch to 5.5.0
authorHans Dedecker <dedeckeh@gmail.com>
Mon, 4 Feb 2019 07:48:01 +0000 (08:48 +0100)
committerHans Dedecker <dedeckeh@gmail.com>
Mon, 4 Feb 2019 08:35:11 +0000 (09:35 +0100)
commitb88907e62a28f2afd30998007fbd4df88ef9f78f
tree72d453d3421e9aa2165d5a37910d48e487307a81
parent646d28f996378c2ae49f58f5eb06760c406951aa
toolchain/gcc: backport FORTIFY patch to 5.5.0

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 <dedeckeh@gmail.com>
toolchain/gcc/patches/5.5.0/050-libitm-Don-t-redefine-__always_inline-in-local_atomi.patch [new file with mode: 0644]