From: Indu Bhagat <indu.bhagat@oracle.com>
To: gcc-patches@gcc.gnu.org
Subject: [COMMITTED] ctfout: use ctfc_get_num_ctf_vars instead
Date: Mon, 28 Mar 2022 14:10:03 -0700 [thread overview]
Message-ID: <20220328211003.444088-1-indu.bhagat@oracle.com> (raw)
[Committed as obvious.]
A minor cosmetic fix.
2022-03-28 Indu Bhagat <indu.bhagat@oracle.com>
gcc/ChangeLog:
* ctfout.cc (ctf_preprocess): Use ctfc_get_num_ctf_vars instead.
(output_ctf_vars): Likewise.
---
gcc/ctfout.cc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/ctfout.cc b/gcc/ctfout.cc
index 9bd918af53c..a23d3775801 100644
--- a/gcc/ctfout.cc
+++ b/gcc/ctfout.cc
@@ -287,7 +287,7 @@ ctf_preprocess (ctf_container_ref ctfc)
ctfc->ctfc_gobjts_list = ggc_vec_alloc<ctf_dvdef_t*>(num_global_objts);
}
- size_t num_ctf_vars = ctfc->ctfc_vars->elements ();
+ size_t num_ctf_vars = ctfc_get_num_ctf_vars (ctfc);
if (num_ctf_vars)
{
ctf_dvd_preprocess_arg_t dvd_arg;
@@ -597,7 +597,7 @@ static void
output_ctf_vars (ctf_container_ref ctfc)
{
size_t i;
- size_t num_ctf_vars = ctfc->ctfc_vars->elements ();
+ size_t num_ctf_vars = ctfc_get_num_ctf_vars (ctfc);
if (num_ctf_vars)
{
/* Iterate over the list of sorted vars and output the asm. */
--
2.31.1
reply other threads:[~2022-03-28 21:10 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=20220328211003.444088-1-indu.bhagat@oracle.com \
--to=indu.bhagat@oracle.com \
--cc=gcc-patches@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: link
Be 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).