[GCC] Commit retpoline patch code, for fixing security issues.

This applies the Intel GCC code patches, to allow compiling
with appropriate flags for mitigating the indirect branch variant of
the speculative execution security flaw.

Bug: None
Test: This is already in place in ChromeOS and has been tested on
the ChromeOS kernels.

Change-Id: Ideffb433b697f1fe7e4ca2c1eaa968160abfcc8b

1 files changed, 0 insertions, 20 deletions

diff --git a/gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-force-patching.c b/gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-force-patching.c
deleted file mode 100644
index 86ad1594c..000000000
--- a/gcc-4.9/gcc/testsuite/gcc.target/i386/patch-functions-force-patching.c
+++ /dev/null
@@ -1,20 +0,0 @@
-/* { dg-do compile } */
-/* { dg-require-effective-target lp64 } */
-/* { dg-options "-O3 -mpatch-functions-for-instrumentation -mno-patch-functions-main-always" } */
-
-/* Functions which have the always_patch attribute should be patched no matter
-   what.  Check that there are nop-bytes at the beginning and end of the
-   function.  We add -O3 so that the compiler will try to inline foo (but it
-   will be blocked by the attribute).  */
-
-/* { dg-final { scan-assembler ".byte\t0xeb,0x09(.*).byte\t0x90" } } */
-/* { dg-final { scan-assembler "ret(.*).byte\t0x90(.*).byte\t0x90" } } */
-
-__attribute__ ((always_patch_for_instrumentation))
-static int foo () {
-  return 3;
-}
-
-int main () {
-  volatile int x = foo ();
-}