From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 1851) id 86FD43858D32; Mon, 5 Sep 2022 09:21:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 86FD43858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1662369684; bh=qMSDwHI1A60qPoDsWStnBQvrTDNLPHVRkyjbTT+xwuw=; h=From:To:Subject:Date:From; b=YuXZTnTkVO4p8eFsaKwvppCupoFtOW7MpX+Ro1qv49oo908ttr9/+P7Owvq5eiK/1 r20yaWUBd0Gx5McSe6TFIwA594ueAzuSZuzHANfObLFR3Nf0Fza1irRV1ZQw5YAYMG wNirOvCg07bmQJer8yFu6785yWvPBXHw0w7SNOyI= MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" From: Martin Liska To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-2432] docs: rename DEBUGGER_REGISTER_NUMBER in texi X-Act-Checkin: gcc X-Git-Author: Martin Liska X-Git-Refname: refs/heads/master X-Git-Oldrev: ca60bd93e216ae0425f790e1d4f4dc4a48763c0e X-Git-Newrev: 9c805ddf66a1cfc93e6cc65f768897da2bc303ed Message-Id: <20220905092124.86FD43858D32@sourceware.org> Date: Mon, 5 Sep 2022 09:21:24 +0000 (GMT) List-Id: https://gcc.gnu.org/g:9c805ddf66a1cfc93e6cc65f768897da2bc303ed commit r13-2432-g9c805ddf66a1cfc93e6cc65f768897da2bc303ed Author: Martin Liska Date: Mon Sep 5 11:20:38 2022 +0200 docs: rename DEBUGGER_REGISTER_NUMBER in texi gcc/ChangeLog: * doc/tm.texi.in: Rename DEBUGGER_REGISTER_NUMBER to DEBUGGER_REGNO. * doc/tm.texi: Regenerate. Diff: --- gcc/doc/tm.texi | 8 ++++---- gcc/doc/tm.texi.in | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/gcc/doc/tm.texi b/gcc/doc/tm.texi index f8fce277eb5..e47bf28089a 100644 --- a/gcc/doc/tm.texi +++ b/gcc/doc/tm.texi @@ -3785,7 +3785,7 @@ Define this macro if the target's representation for dwarf registers used in .eh_frame or .debug_frame is different from that used in other debug info sections. Given a GCC hard register number, this macro should return the .eh_frame register number. The default is -@code{DEBUGGER_REGISTER_NUMBER (@var{regno})}. +@code{DEBUGGER_REGNO (@var{regno})}. @end defmac @@ -9948,7 +9948,7 @@ This describes how to specify debugging information. @c prevent bad page break with this line These macros affect all debugging formats. -@defmac DEBUGGER_REGISTER_NUMBER (@var{regno}) +@defmac DEBUGGER_REGNO (@var{regno}) A C expression that returns the debugger register number for the compiler register number @var{regno}. In the default macro provided, the value of this expression will be @var{regno} itself. But sometimes there are @@ -9958,11 +9958,11 @@ compiler and another for debugger@. If two registers have consecutive numbers inside GCC, and they can be used as a pair to hold a multiword value, then they @emph{must} have -consecutive numbers after renumbering with @code{DEBUGGER_REGISTER_NUMBER}. +consecutive numbers after renumbering with @code{DEBUGGER_REGNO}. Otherwise, debuggers will be unable to access such a pair, because they expect register pairs to be consecutive in their own numbering scheme. -If you find yourself defining @code{DEBUGGER_REGISTER_NUMBER} in way that +If you find yourself defining @code{DEBUGGER_REGNO} in way that does not preserve register pairs, then what you must do instead is redefine the actual register numbering scheme. @end defmac diff --git a/gcc/doc/tm.texi.in b/gcc/doc/tm.texi.in index 955343ab86e..5312059ea79 100644 --- a/gcc/doc/tm.texi.in +++ b/gcc/doc/tm.texi.in @@ -3012,7 +3012,7 @@ Define this macro if the target's representation for dwarf registers used in .eh_frame or .debug_frame is different from that used in other debug info sections. Given a GCC hard register number, this macro should return the .eh_frame register number. The default is -@code{DEBUGGER_REGISTER_NUMBER (@var{regno})}. +@code{DEBUGGER_REGNO (@var{regno})}. @end defmac @@ -6618,7 +6618,7 @@ This describes how to specify debugging information. @c prevent bad page break with this line These macros affect all debugging formats. -@defmac DEBUGGER_REGISTER_NUMBER (@var{regno}) +@defmac DEBUGGER_REGNO (@var{regno}) A C expression that returns the debugger register number for the compiler register number @var{regno}. In the default macro provided, the value of this expression will be @var{regno} itself. But sometimes there are @@ -6628,11 +6628,11 @@ compiler and another for debugger@. If two registers have consecutive numbers inside GCC, and they can be used as a pair to hold a multiword value, then they @emph{must} have -consecutive numbers after renumbering with @code{DEBUGGER_REGISTER_NUMBER}. +consecutive numbers after renumbering with @code{DEBUGGER_REGNO}. Otherwise, debuggers will be unable to access such a pair, because they expect register pairs to be consecutive in their own numbering scheme. -If you find yourself defining @code{DEBUGGER_REGISTER_NUMBER} in way that +If you find yourself defining @code{DEBUGGER_REGNO} in way that does not preserve register pairs, then what you must do instead is redefine the actual register numbering scheme. @end defmac