public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r11-9999] Fix modref_tree::remap_params Date: Mon, 16 May 2022 10:05:55 +0000 (GMT) [thread overview] Message-ID: <20220516100555.357D73858C50@sourceware.org> (raw) https://gcc.gnu.org/g:6c9a2db0586f6c7813496be6ec67e60c55b252c3 commit r11-9999-g6c9a2db0586f6c7813496be6ec67e60c55b252c3 Author: Jan Hubicka <jh@suse.cz> Date: Wed Nov 10 10:25:51 2021 +0100 Fix modref_tree::remap_params gcc/ChangeLog: * ipa-modref-tree.h (modref_tree::remap_params): Fix off-by-one error. (cherry picked from commit b406bb901f7e98f7c6d66a240c2eb64b7cd7e615) Diff: --- gcc/ipa-modref-tree.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/ipa-modref-tree.h b/gcc/ipa-modref-tree.h index d36c28c0470..9927fc0982b 100644 --- a/gcc/ipa-modref-tree.h +++ b/gcc/ipa-modref-tree.h @@ -560,7 +560,7 @@ struct GTY((user)) modref_tree size_t k; modref_access_node *access_node; FOR_EACH_VEC_SAFE_ELT (ref_node->accesses, k, access_node) - if (access_node->parm_index > 0) + if (access_node->parm_index >= 0) { if (access_node->parm_index < (int)map->length ()) access_node->parm_index = (*map)[access_node->parm_index];
reply other threads:[~2022-05-16 10:05 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=20220516100555.357D73858C50@sourceware.org \ --to=rguenth@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).