x86: Allow gcc to use the red zone (XCC)
authorBarret Rhoden <brho@cs.berkeley.edu>
Wed, 4 May 2016 19:42:50 +0000 (15:42 -0400)
committerBarret Rhoden <brho@cs.berkeley.edu>
Wed, 4 May 2016 20:13:57 +0000 (16:13 -0400)
Now that pop_user_ctx() can handle the red zone, we don't need to tell
gcc to never use it.

Rebuild your toolchain.

Signed-off-by: Barret Rhoden <brho@cs.berkeley.edu>
tools/compilers/gcc-glibc/gcc-4.9.2-akaros/gcc/config/i386/akaros64.h

index 6f53471..c8cd428 100644 (file)
@@ -35,7 +35,7 @@ see the files COPYING3 and COPYING.RUNTIME respectively.  If not, see
 #define CPP_SPEC "%{posix:-D_POSIX_SOURCE} %{pthread:-D_REENTRANT}"
 
 #undef CC1_SPEC
-#define CC1_SPEC "%(cc1_cpu) %{profile:-p} -mno-red-zone "
+#define CC1_SPEC "%(cc1_cpu) %{profile:-p} "
 
 /* The svr4 ABI for the i386 says that records and unions are returned
    in memory.  In the 64bit compilation we will turn this flag off in