public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Giuliano Belinassi <giulianob@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/autopar_devel] Fix off-by-one error in previous commit Date: Sat, 22 Aug 2020 21:41:20 +0000 (GMT) [thread overview] Message-ID: <20200822214120.22682386102B@sourceware.org> (raw) https://gcc.gnu.org/g:e4a1f22c3b3acb1a8e44d19d8a31b2861eefce4b commit e4a1f22c3b3acb1a8e44d19d8a31b2861eefce4b Author: Eric Botcazou <ebotcazou@gcc.gnu.org> Date: Thu May 28 19:29:42 2020 +0200 Fix off-by-one error in previous commit The bitregion_end field points to the next bit after the region. gcc/ChangeLog * gimple-ssa-store-merging.c (merged_store_group::can_be_merged_into): Fix off-by-one error. Diff: --- gcc/gimple-ssa-store-merging.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/gimple-ssa-store-merging.c b/gcc/gimple-ssa-store-merging.c index 400a0010c34..3ab614148a7 100644 --- a/gcc/gimple-ssa-store-merging.c +++ b/gcc/gimple-ssa-store-merging.c @@ -1874,7 +1874,7 @@ merged_store_group::can_be_merged_into (store_immediate_info *info) || stores[0]->rhs_code == BIT_INSERT_EXPR) && info->bitregion_start == stores[0]->bitregion_start && info->bitregion_end == stores[0]->bitregion_end - && info->bitregion_end - info->bitregion_start < MAX_FIXED_MODE_SIZE) + && info->bitregion_end - info->bitregion_start <= MAX_FIXED_MODE_SIZE) return true; if (stores[0]->rhs_code == MEM_REF @@ -1882,7 +1882,7 @@ merged_store_group::can_be_merged_into (store_immediate_info *info) || info->rhs_code == BIT_INSERT_EXPR) && info->bitregion_start == stores[0]->bitregion_start && info->bitregion_end == stores[0]->bitregion_end - && info->bitregion_end - info->bitregion_start < MAX_FIXED_MODE_SIZE) + && info->bitregion_end - info->bitregion_start <= MAX_FIXED_MODE_SIZE) return true; return false;
reply other threads:[~2020-08-22 21:41 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=20200822214120.22682386102B@sourceware.org \ --to=giulianob@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).