This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: deconsting reg_names
- To: gcc-patches at gcc dot gnu dot org
- Subject: Re: deconsting reg_names
- From: Nick Clifton <nickc at cygnus dot com>
- Date: Sun, 28 May 2000 11:55:21 -0700
Hi Richard,
: Quite a few targets modify reg_names at runtime. This
: is documented to work.
Since reg_names can be modified, how about this small patch to the
documentation saying that it is OK to modify it inside
CONDITIONAL_REGISTER_UAGE ?
Cheers
Nick
2000-05-28 Nick Clifton <nickc@cygnus.com>
* tm.texi (CONDITIONAL_REGISTER_USAGE): Document that it can
modify reg_names.
Index: gcc/tm.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/tm.texi,v
retrieving revision 1.124
diff -p -r1.124 tm.texi
*** tm.texi 2000/05/01 16:53:03 1.124
--- tm.texi 2000/05/28 18:52:58
*************** preserve the entire contents of a regist
*** 1406,1419 ****
@findex fixed_regs
@findex call_used_regs
@item CONDITIONAL_REGISTER_USAGE
! Zero or more C statements that may conditionally modify four variables
! @code{fixed_regs}, @code{call_used_regs}, @code{global_regs}
! (these three are of type @code{char []}) and @code{reg_class_contents}
! (of type @code{HARD_REG_SET}).
Before the macro is called @code{fixed_regs}, @code{call_used_regs}
! and @code{reg_class_contents} have been initialized from
! @code{FIXED_REGISTERS}, @code{CALL_USED_REGISTERS} and
! @code{REG_CLASS_CONTENTS}, respectively,
@code{global_regs} has been cleared, and any @samp{-ffixed-@var{reg}},
@samp{-fcall-used-@var{reg}} and @samp{-fcall-saved-@var{reg}} command
options have been applied.
--- 1406,1420 ----
@findex fixed_regs
@findex call_used_regs
@item CONDITIONAL_REGISTER_USAGE
! Zero or more C statements that may conditionally modify five variables
! @code{fixed_regs}, @code{call_used_regs}, @code{global_regs},
! (these three are of type @code{char []}), @code{reg_names} (of type
! @code{char * const[]}) and @code{reg_class_contents} (of type
! @code{HARD_REG_SET}).
Before the macro is called @code{fixed_regs}, @code{call_used_regs}
! @code{reg_class_contents} and @code{reg_names} have been initialized
! from @code{FIXED_REGISTERS}, @code{CALL_USED_REGISTERS},
! @code{REG_CLASS_CONTENTS} and @code{REGISTER_NAMES}, respectively,
@code{global_regs} has been cleared, and any @samp{-ffixed-@var{reg}},
@samp{-fcall-used-@var{reg}} and @samp{-fcall-saved-@var{reg}} command
options have been applied.