From: Richard Sandiford <richard.sandiford@googlemail.com>
To: Martin Sebor <msebor@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] fix ICE in generic_overlap (PR 84526)
Date: Tue, 27 Feb 2018 12:33:00 -0000 [thread overview]
Message-ID: <87po4qbojt.fsf@e105548-lin.cambridge.arm.com> (raw)
In-Reply-To: <63d4e234-627f-c713-202c-1aac7ba32b2f@gmail.com> (Martin Sebor's message of "Mon, 26 Feb 2018 10:32:27 -0700")
Martin Sebor <msebor@gmail.com> writes:
> + /* Convert the poly_int64 offset to to offset_int. The offset
> + should be constant but be prepared for it not to be just in
> + case. */
This comment seems redundant and could easily get out of date once
ACLE support is added.
> + offset_int cstoff;
> + if (bytepos.is_constant (&cstoff))
> {
> - base = get_base_address (TREE_OPERAND (expr, 0));
> - return;
> + offrange[0] += cstoff;
> + offrange[1] += cstoff;
Although this looks right, there's no actual need for cstoff to be
offset_int here, and I think the original HOST_WIDE_INT was more
efficient.
I realise you reuse the cstoff variable later with wi::to_offset,
but it doesn't seem necessary to use the same variable, since it's
logically a separate value.
Either way's fine, just thought I'd mention it :-)
Thanks,
Richard
next prev parent reply other threads:[~2018-02-27 12:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 19:57 Martin Sebor
2018-02-23 20:49 ` Jakub Jelinek
2018-02-23 21:46 ` Martin Sebor
2018-02-24 9:32 ` Richard Sandiford
2018-02-24 14:45 ` Martin Sebor
2018-02-25 10:03 ` Richard Sandiford
2018-02-24 12:49 ` Jakub Jelinek
2018-02-23 23:25 ` Martin Sebor
2018-02-26 17:32 ` Martin Sebor
2018-02-26 20:49 ` Jakub Jelinek
2018-02-26 18:13 ` Martin Sebor
2018-03-07 15:17 ` Martin Sebor
2018-02-27 12:33 ` Richard Sandiford [this message]
2018-03-07 19:37 ` Jeff Law
2018-03-07 22:52 ` Martin Sebor
2018-03-07 23:04 ` Richard Sandiford
2018-03-07 23:59 ` Martin Sebor
2018-03-09 19:07 ` Jeff Law
2018-03-07 19:18 ` Jeff Law
2018-03-07 19:14 ` Jeff Law
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=87po4qbojt.fsf@e105548-lin.cambridge.arm.com \
--to=richard.sandiford@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=msebor@gmail.com \
/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).