public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-7840] predcom: Fix up component::component [PR105056] Date: Mon, 28 Mar 2022 07:52:47 +0000 (GMT) [thread overview] Message-ID: <20220328075247.CC7433858C56@sourceware.org> (raw) https://gcc.gnu.org/g:50f9148f7a8daf1fa1608cb23595c3cca191da0f commit r12-7840-g50f9148f7a8daf1fa1608cb23595c3cca191da0f Author: Jakub Jelinek <jakub@redhat.com> Date: Mon Mar 28 09:51:28 2022 +0200 predcom: Fix up component::component [PR105056] The recent change didn't initialize comp_step while previously we used XCNEW to allocate it. I think RS_ANY is better than RS_INTERNAL (== 0) as the default. 2022-03-28 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/105056 * tree-predcom.cc (component::component): Initialize also comp_step. Diff: --- gcc/tree-predcom.cc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gcc/tree-predcom.cc b/gcc/tree-predcom.cc index e4aea7cdcb4..bb3a1cb68fc 100644 --- a/gcc/tree-predcom.cc +++ b/gcc/tree-predcom.cc @@ -367,7 +367,8 @@ enum ref_step_type struct component { - component (bool es) : eliminate_store_p (es), next (NULL) {} + component (bool es) : comp_step (RS_ANY), eliminate_store_p (es), + next (NULL) {} /* The references in the component. */ auto_vec<dref> refs;
reply other threads:[~2022-03-28 7:52 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=20220328075247.CC7433858C56@sourceware.org \ --to=jakub@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).