johannes    02/09/12 18:08:09

  Modified:    gcc      calls.c
  Log:
  Remove a turly hack that is superseded by a better fix from rth.
  
  Revision  Changes    Path
  1.37      +0 -24     gcc3/gcc/calls.c
  
  Index: calls.c
  ===================================================================
  RCS file: /cvs/Darwin/gcc3/gcc/calls.c,v
  retrieving revision 1.36
  retrieving revision 1.37
  diff -u -r1.36 -r1.37
  --- calls.c   2002/09/10 20:53:19     1.36
  +++ calls.c   2002/09/13 01:08:08     1.37
  @@ -4482,32 +4482,8 @@
         we actually expand the argument since the expansion itself may
         trigger library calls which might need to use the same stack slot.  */
         if (argblock && ! variable_size && arg->stack)
  -     /* APPLE LOCAL begin pass-struct-by-value fix  */
  -     /* 2.95 comments retained for amusement value.  This is FSF PR 6241;
  -        no doubt a cleaner fix will come along  --dj */
  -#if defined(TARGET_MACHO)             /* Sorry :-(  */
  -     /* (Ahem, Cough) "Fix" for some really mondo weirdnesses we have on
  -        PPC when passing a struct >32 bytes as a value parameter.
  -        memcpy () ends up being called to copy the struct onto the stack,
  -        but wants to save and restore the 32-byte REG_PARM_STACK_SPACE.
  -        Bad news if the memcpy destination and this 32-byte
  -        REG_PARM_STACK_SPACE overlap...
  - 
  -        Try to avoid this unnecessary save/restore by not marking the 32
  -        byte area as "dirty".  */
  - 
  -     {
  -       if (upper_bound - reg_parm_stack_space > lower_bound)
  -         for (i = MAX (lower_bound, reg_parm_stack_space);
  -              i < upper_bound; i++)
  -           stack_usage_map[i] = 1;
  -       else
  -#endif
  -     /* APPLE LOCAL end pass-struct-by-value fix  */
        for (i = lower_bound; i < upper_bound; i++)
          stack_usage_map[i] = 1;
  -     /* APPLE LOCAL pass-struct-by-value fix  */
  -     }
       }
   
     /* If this isn't going to be placed on both the stack and in registers,
  
  
  


Reply via email to