From: Jan Hubicka Date: Fri, 3 Aug 2007 23:07:25 +0000 (+0200) Subject: i386.c (setup_incoming_varargs_64): Tolerate 64bit preferred stack boundary. X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=48dd736cd4f9fe8eddc5ef1ab7711021236eacc4;p=platform%2Fupstream%2Fgcc.git i386.c (setup_incoming_varargs_64): Tolerate 64bit preferred stack boundary. * i386.c (setup_incoming_varargs_64): Tolerate 64bit preferred stack boundary. From-SVN: r127189 --- diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 05e5dcc..5878f50 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2007-08-03 Jan Hubicka + + * i386.c (setup_incoming_varargs_64): Tolerate 64bit preferred + stack boundary. + 2007-08-03 David Edelsohn * config/rs6000/rs6000.c (struct processor_cost): Change diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c index 28471ba..de03780 100644 --- a/gcc/config/i386/i386.c +++ b/gcc/config/i386/i386.c @@ -4694,7 +4694,14 @@ setup_incoming_varargs_64 (CUMULATIVE_ARGS *cum) /* Indicate to allocate space on the stack for varargs save area. */ ix86_save_varrargs_registers = 1; - cfun->stack_alignment_needed = 128; + /* We need 16-byte stack alignment to save SSE registers. If user + asked for lower preferred_stack_boundary, lets just hope that he knows + what he is doing and won't varargs SSE values. + + We also may end up assuming that only 64bit values are stored in SSE + register let some floating point program work. */ + if (ix86_preferred_stack_boundary >= 128) + cfun->stack_alignment_needed = 128; save_area = frame_pointer_rtx; set = get_varargs_alias_set ();