public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Kewen Lin <linkw@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-3468] rs6000: Remove typedef for struct rs6000_cost_data Date: Mon, 13 Sep 2021 06:30:07 +0000 (GMT) [thread overview] Message-ID: <20210913063007.5243E3858D35@sourceware.org> (raw) https://gcc.gnu.org/g:b70e2541fec8751d287b24b9e3681a41e420d4c4 commit r12-3468-gb70e2541fec8751d287b24b9e3681a41e420d4c4 Author: Kewen Lin <linkw@linux.ibm.com> Date: Sun Sep 12 21:04:31 2021 -0500 rs6000: Remove typedef for struct rs6000_cost_data As Segher pointed out, to typedef struct _rs6000_cost_data as rs6000_cost_data is useless, so rewrite it without typedef. gcc/ChangeLog: * config/rs6000/rs6000.c (struct rs6000_cost_data): Remove typedef. (rs6000_init_cost): Adjust. Diff: --- gcc/config/rs6000/rs6000.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000/rs6000.c index b7ea1483da5..39d428db8e6 100644 --- a/gcc/config/rs6000/rs6000.c +++ b/gcc/config/rs6000/rs6000.c @@ -5262,7 +5262,7 @@ rs6000_preferred_simd_mode (scalar_mode mode) return word_mode; } -typedef struct _rs6000_cost_data +struct rs6000_cost_data { struct loop *loop_info; unsigned cost[3]; @@ -5271,7 +5271,7 @@ typedef struct _rs6000_cost_data bool vect_nonmem; /* Indicates this is costing for the scalar version of a loop or block. */ bool costing_for_scalar; -} rs6000_cost_data; +}; /* Test for likely overcommitment of vector hardware resources. If a loop iteration is relatively large, and too large a percentage of @@ -5337,7 +5337,7 @@ rs6000_density_test (rs6000_cost_data *data) static void * rs6000_init_cost (struct loop *loop_info, bool costing_for_scalar) { - rs6000_cost_data *data = XNEW (struct _rs6000_cost_data); + rs6000_cost_data *data = XNEW (rs6000_cost_data); data->loop_info = loop_info; data->cost[vect_prologue] = 0; data->cost[vect_body] = 0;
reply other threads:[~2021-09-13 6:30 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=20210913063007.5243E3858D35@sourceware.org \ --to=linkw@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).