From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/2] simplify CBR-CBR on the same condition
Date: Tue, 17 Nov 2020 02:10:56 +0100 [thread overview]
Message-ID: <20201117011058.53995-1-luc.vanoostenryck@gmail.com> (raw)
These two patches do the the CBR-CBR 'diamond' simplification.
Together with the previous series, it shaves a few more
'context imbalance' warnings but I think it will need to handle
phi-sources to show its full potential.
Luc Van Oostenryck (2):
rebuild dominance tree during CFG cleanup
simplify CBR-CBR on the same condition
flow.c | 106 +++++++++++++++++++++++++++++++++++++++++++++++++++++
optimize.c | 10 ++++-
2 files changed, 114 insertions(+), 2 deletions(-)
--
2.29.2
next reply other threads:[~2020-11-17 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 1:10 Luc Van Oostenryck [this message]
2020-11-17 1:10 ` [PATCH 1/2] rebuild dominance tree during CFG cleanup Luc Van Oostenryck
2020-11-17 1:10 ` [PATCH 2/2] simplify CBR-CBR on the same condition Luc Van Oostenryck
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=20201117011058.53995-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=torvalds@linux-foundation.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 NNTP newsgroup(s).