--- Comment #10 from hjl at gcc dot gnu dot org 2010-09-07 21:19 ---
Subject: Bug 42313
Author: hjl
Date: Tue Sep 7 21:18:55 2010
New Revision: 163971
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=163971
Log:
Redefine STACK_BOUNDARY/PREFERRED_STACK_BOUNDARY for Darwin/x86.
--- Comment #11 from howarth at nitro dot med dot uc dot edu 2010-09-08
01:05 ---
Fixed on trunk at r163971.
--
howarth at nitro dot med dot uc dot edu changed:
What|Removed |Added
--- Comment #8 from howarth at nitro dot med dot uc dot edu 2010-09-04
19:13 ---
(In reply to comment #7)
I fixed the test case to not expect the unimplemented optimization in r157197,
however, it would be nice to ensure the async signal handlers can handle
unaligned stacks and to
--- Comment #9 from howarth at nitro dot med dot uc dot edu 2010-09-04
21:20 ---
Updated patch to reflect the wider coverage of PRs fixed...
http://gcc.gnu.org/ml/gcc-patches/2010-09/msg00365.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42313
--- Comment #7 from mikestump at comcast dot net 2010-03-03 16:56 ---
I fixed the test case to not expect the unimplemented optimization in r157197,
however, it would be nice to ensure the async signal handlers can handle
unaligned stacks and to perform this optimization. I'm fairly
--- Comment #6 from pinskia at gcc dot gnu dot org 2009-12-08 19:51 ---
I think this comes down to an alignment issue. On darwin, the stack has to be
aligned to 16bytes so something inside i386.c is deciding that we to allocate
the stack frame as there was something on the stack and we
