diff options
author | Kito Cheng <kito@0xlab.org> | 2014-08-24 02:52:46 +0000 |
---|---|---|
committer | Chung-Ju Wu <jasonwucj@gcc.gnu.org> | 2014-08-24 02:52:46 +0000 |
commit | ef24330ddfb1206a90cf44bdda2d941abc05d5d3 (patch) | |
tree | 876929a915d59c4c5cd72a5c23aa427680d8f595 /gcc/doc | |
parent | 3447fefe74d4f1f1c08698f04123a9c699c47f71 (diff) | |
download | gcc-ef24330ddfb1206a90cf44bdda2d941abc05d5d3.zip gcc-ef24330ddfb1206a90cf44bdda2d941abc05d5d3.tar.gz gcc-ef24330ddfb1206a90cf44bdda2d941abc05d5d3.tar.bz2 |
Remove CALLER_SAVE_PROFITABLE since it is not used at present.
* system.h (CALLER_SAVE_PROFITABLE): Poison.
* regs.h (CALLER_SAVE_PROFITABLE): Remove.
* doc/tm.texi.in (CALLER_SAVE_PROFITABLE): Remove.
* doc/tm.texi: Regenerate.
From-SVN: r214405
Diffstat (limited to 'gcc/doc')
-rw-r--r-- | gcc/doc/tm.texi | 10 | ||||
-rw-r--r-- | gcc/doc/tm.texi.in | 10 |
2 files changed, 0 insertions, 20 deletions
diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi index 9dd8d68..4d6492b 100644 --- a/gcc/doc/tm.texi +++ b/gcc/doc/tm.texi @@ -4528,16 +4528,6 @@ If you enable it, GCC can save registers around function calls. This makes it possible to use call-clobbered registers to hold variables that must live across calls. -@defmac CALLER_SAVE_PROFITABLE (@var{refs}, @var{calls}) -A C expression to determine whether it is worthwhile to consider placing -a pseudo-register in a call-clobbered hard register and saving and -restoring it around each function call. The expression should be 1 when -this is worth doing, and 0 otherwise. - -If you don't define this macro, a default is used which is good on most -machines: @code{4 * @var{calls} < @var{refs}}. -@end defmac - @defmac HARD_REGNO_CALLER_SAVE_MODE (@var{regno}, @var{nregs}) A C expression specifying which mode is required for saving @var{nregs} of a pseudo-register in call-clobbered hard register @var{regno}. If diff --git a/gcc/doc/tm.texi.in b/gcc/doc/tm.texi.in index dd72b98..7a63353 100644 --- a/gcc/doc/tm.texi.in +++ b/gcc/doc/tm.texi.in @@ -3683,16 +3683,6 @@ If you enable it, GCC can save registers around function calls. This makes it possible to use call-clobbered registers to hold variables that must live across calls. -@defmac CALLER_SAVE_PROFITABLE (@var{refs}, @var{calls}) -A C expression to determine whether it is worthwhile to consider placing -a pseudo-register in a call-clobbered hard register and saving and -restoring it around each function call. The expression should be 1 when -this is worth doing, and 0 otherwise. - -If you don't define this macro, a default is used which is good on most -machines: @code{4 * @var{calls} < @var{refs}}. -@end defmac - @defmac HARD_REGNO_CALLER_SAVE_MODE (@var{regno}, @var{nregs}) A C expression specifying which mode is required for saving @var{nregs} of a pseudo-register in call-clobbered hard register @var{regno}. If |