public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-2432] docs: rename DEBUGGER_REGISTER_NUMBER in texi Date: Mon, 5 Sep 2022 09:21:24 +0000 (GMT) [thread overview] Message-ID: <20220905092124.86FD43858D32@sourceware.org> (raw) https://gcc.gnu.org/g:9c805ddf66a1cfc93e6cc65f768897da2bc303ed commit r13-2432-g9c805ddf66a1cfc93e6cc65f768897da2bc303ed Author: Martin Liska <mliska@suse.cz> 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
reply other threads:[~2022-09-05 9:21 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220905092124.86FD43858D32@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).