This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[patch] Don't mention STRICT_ARGUMENT_NAMING in comments.


Hi,

Attached is a patch to replace STRICT_ARGUMENT_NAMING in comments with
targetm.calls.strict_argument_naming() as we don't use
STRICT_ARGUMENT_NAMING directly in machine-independent code.

Committed as obvious.

Kazu Hirata

2004-01-14  Kazu Hirata  <kazu@cs.umass.edu>

	* calls.c: Replace STRICT_ARGUMENT_NAMING in comments with
	targetm.calls.strict_argument_naming().
	* target.h: Likewise.

Index: calls.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/calls.c,v
retrieving revision 1.312
diff -c -r1.312 calls.c
*** calls.c	24 Dec 2003 06:52:24 -0000	1.312
--- calls.c	14 Jan 2004 21:56:23 -0000
***************
*** 2405,2420 ****
  
    /* Compute number of named args.
       Normally, don't include the last named arg if anonymous args follow.
!      We do include the last named arg if STRICT_ARGUMENT_NAMING is nonzero.
       (If no anonymous args follow, the result of list_length is actually
       one too large.  This is harmless.)
  
       If targetm.calls.pretend_outgoing_varargs_named() returns
!      nonzero, and STRICT_ARGUMENT_NAMING is zero, this machine will be
!      able to place unnamed args that were passed in registers into the
!      stack.  So treat all args as named.  This allows the insns
!      emitting for a specific argument list to be independent of the
!      function declaration.
  
       If targetm.calls.pretend_outgoing_varargs_named() returns zero,
       we do not have any reliable way to pass unnamed args in
--- 2405,2421 ----
  
    /* Compute number of named args.
       Normally, don't include the last named arg if anonymous args follow.
!      We do include the last named arg if
!      targetm.calls.strict_argument_naming() returns nonzero.
       (If no anonymous args follow, the result of list_length is actually
       one too large.  This is harmless.)
  
       If targetm.calls.pretend_outgoing_varargs_named() returns
!      nonzero, and targetm.calls.strict_argument_naming() returns zero,
!      this machine will be able to place unnamed args that were passed
!      in registers into the stack.  So treat all args as named.  This
!      allows the insns emitting for a specific argument list to be
!      independent of the function declaration.
  
       If targetm.calls.pretend_outgoing_varargs_named() returns zero,
       we do not have any reliable way to pass unnamed args in
Index: target.h
===================================================================
RCS file: /cvs/gcc/gcc/gcc/target.h,v
retrieving revision 1.73
diff -c -r1.73 target.h
*** target.h	4 Dec 2003 09:11:17 -0000	1.73
--- target.h	14 Jan 2004 21:56:24 -0000
***************
*** 433,439 ****
  				    tree type, int *pretend_arg_size, int second_time);
      bool (*strict_argument_naming) (CUMULATIVE_ARGS *ca);
      /* Returns true if we should use SETUP_INCOMING_VARARGS and/or
!        STRICT_ARGUMENT_NAMING.  */
      bool (*pretend_outgoing_varargs_named) (CUMULATIVE_ARGS *ca);
    } calls;
  };
--- 433,439 ----
  				    tree type, int *pretend_arg_size, int second_time);
      bool (*strict_argument_naming) (CUMULATIVE_ARGS *ca);
      /* Returns true if we should use SETUP_INCOMING_VARARGS and/or
!        targetm.calls.strict_argument_naming().  */
      bool (*pretend_outgoing_varargs_named) (CUMULATIVE_ARGS *ca);
    } calls;
  };


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]