All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/2] floating-point literals
Date: Wed, 12 Apr 2017 11:29:25 +0200	[thread overview]
Message-ID: <20170412092927.23884-1-luc.vanoostenryck@gmail.com> (raw)

The goal of this series is to simplify the handling
of floating-point literals and as an added bonus, to
make possible the CSE of those literals.

This series is available at:
	git://github.com/lucvoo/sparse.git cse-setfval
based on commit:
	604e7ef9c37100c4ca3dc0b3bee00d114e265684 (fix-f2i-casts)
up to commit:
	c9585071d02590f40175ea90c395d15ef70e9a1e

Luc Van Oostenryck (2):
  add OP_SETFVAL
  CSE: support CSE of floating-point literal

 Documentation/instructions.txt      | 12 ++++++----
 cse.c                               | 11 +++++++++
 linearize.c                         | 18 ++++++++++----
 linearize.h                         |  4 ++++
 liveness.c                          |  1 +
 simplify.c                          |  1 +
 sparse-llvm.c                       | 16 +++++++++----
 validation/cast-constant-to-float.c |  6 ++---
 validation/cast-constants.c         | 20 ++++++++--------
 validation/fp-ops.c                 |  2 +-
 validation/optim/bool-context-fp.c  | 47 +++++++++++++++++++++++++++++++++++++
 validation/optim/cse-setfval.c      | 12 ++++++++++
 12 files changed, 123 insertions(+), 27 deletions(-)
 create mode 100644 validation/optim/bool-context-fp.c
 create mode 100644 validation/optim/cse-setfval.c

-- 
2.12.0


             reply	other threads:[~2017-04-12  9:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  9:29 Luc Van Oostenryck [this message]
2017-04-12  9:29 ` [PATCH 1/2] add OP_SETFVAL Luc Van Oostenryck
2017-04-12  9:29 ` [PATCH 2/2] CSE: support CSE of floating-point literal 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=20170412092927.23884-1-luc.vanoostenryck@gmail.com \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.