------- Comment #30 from howarth at nitro dot med dot uc dot edu 2010-09-01
05:34 -------
With only gcc-pr45234-2.patch at r163712 , I am seeing the following
regressions...
FAIL: gcc.c-torture/execute/builtins/sprintf-chk.c compilation, -Os (internal
compiler error)
FAIL: gcc.dg/stack-usage-1.c scan-file foo\t(256|264)\tstatic
FAIL: gcc.target/i386/stack-usage-realign.c scan-file main\t48\tdynamic,bounded
whereas with gcc-pr45234-2.patch and...
Index: gcc/config/i386/darwin.h
===================================================================
--- gcc/config/i386/darwin.h (revision 163704)
+++ gcc/config/i386/darwin.h (working copy)
@@ -78,9 +78,6 @@
/* On Darwin, the stack is 128-bit aligned at the point of every call.
Failure to ensure this will lead to a crash in the system libraries
or dynamic loader. */
-#undef STACK_BOUNDARY
-#define STACK_BOUNDARY 128
-
#undef MAIN_STACK_BOUNDARY
#define MAIN_STACK_BOUNDARY 128
@@ -91,7 +88,7 @@
it's below the minimum. */
#undef PREFERRED_STACK_BOUNDARY
#define PREFERRED_STACK_BOUNDARY \
- MAX (STACK_BOUNDARY, ix86_preferred_stack_boundary)
+ MAX (128, ix86_preferred_stack_boundary)
/* We want -fPIC by default, unless we're using -static to compile for
the kernel or some such. */
I see the regressions...
FAIL: gcc.dg/nest.c execution test
FAIL: gcc.target/i386/stack-usage-realign.c scan-file main\t48\tdynamic,bounded
FAIL: gcc.target/i386/stack-usage-realign.c scan-file main\t48\tdynamic,bounded
suggesting that the nest.c failure is the only one introduced by the darwin.h
changes
and the remainder are due to gcc-pr45234-2.patch.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36502
