From: Jakub Jelinek <jakub@redhat.com>
To: Andrew MacLeod <amacleod@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 2/6] gimple-range-edge
Date: Mon, 5 Oct 2020 14:09:21 +0200 [thread overview]
Message-ID: <20201005120921.GP2176@tucnak> (raw)
In-Reply-To: <275d2bce-1548-978e-c062-130dd81f88fd@redhat.com>
On Fri, Oct 02, 2020 at 12:59:54PM -0400, Andrew MacLeod via Gcc-patches wrote:
>
> The ranger is needed to map those values to the switch variable, and also
> apply any previous ranges or derived values (ie, if you ask for the range of
> 'y' in case 2, it will return unsigned int [6,6].
>
> * gimple-range-edge.h: New File.
> (outgoing_range): Calculate/cache constant outgoing edge ranges.
>
> * gimple-range-edge.cc: New file.
> (gimple_outgoing_range_stmt_p): New. Find control statement.
> (outgoing_range::outgoing_range): New.
> (outgoing_range::~outgoing_range): New.
> (outgoing_range::get_edge_range): New. Internal switch edge query.
> (outgoing_range::calc_switch_ranges): New. Calculate switch ranges.
> (outgoing_range::edge_range_p): New. Find constant range on edge.
Just a ChangeLog comment (ditto for several other patches).
When you add a new file, just say that and nothing else, i.e.
* gimple-range-edge.h: New File.
* gimple-range-edge.cc: New file.
and that's it. Everything in the new file is new, no need to state it
explicitly.
Jakub
next prev parent reply other threads:[~2020-10-05 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 16:56 Project Ranger Submission / On Demand VRP Andrew MacLeod
2020-10-02 16:58 ` [PATCH 1/6] Ranger patches Andrew MacLeod
2020-10-02 16:59 ` [PATCH 2/6] gimple-range-edge Andrew MacLeod
2020-10-05 12:09 ` Jakub Jelinek [this message]
2020-10-05 13:15 ` Andrew MacLeod
2020-10-02 17:01 ` [PATCH 3/6] gimple-range-gori Andrew MacLeod
2020-10-02 17:02 ` [PATCH 4/6] gimple-range-cache Andrew MacLeod
2020-10-02 17:04 ` [PATCH 5/6] gimple-range Andrew MacLeod
2020-10-02 17:06 ` [PATCH 6/6] Hybrid EVRP Andrew MacLeod
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=20201005120921.GP2176@tucnak \
--to=jakub@redhat.com \
--cc=amacleod@redhat.com \
--cc=gcc-patches@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: 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).