From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [RFC PATCH 0/2] use a single multiplication instruction
Date: Sun, 18 Feb 2018 10:15:17 +0100 [thread overview]
Message-ID: <20180218091519.6708-1-luc.vanoostenryck@gmail.com> (raw)
These two patches replace the instrcutions for signed & unsigned
multiplication (OP_MULS & OP_MULU) by a single one: OP_MUL.
There is no reasons to have both since the IR doesn't do
full/widening multiplication.
Luc Van Oostenryck (2):
unsigned multiplication is also associative
no need for signed & unsigned multiplication
Documentation/IR.md | 7 ++-----
cse.c | 4 ++--
example.c | 5 ++---
linearize.c | 9 ++++-----
linearize.h | 2 +-
opcode.c | 3 +--
simplify.c | 15 +++++----------
sparse-llvm.c | 6 +-----
validation/int128.c | 2 +-
9 files changed, 19 insertions(+), 34 deletions(-)
--
2.16.0
next reply other threads:[~2018-02-18 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 9:15 Luc Van Oostenryck [this message]
2018-02-18 9:15 ` [RFC PATCH 1/2] unsigned multiplication is also associative Luc Van Oostenryck
2018-02-18 9:15 ` [RFC PATCH 2/2] no need for signed & unsigned multiplication 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=20180218091519.6708-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.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).