From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/9] division by zero warnings
Date: Wed, 31 May 2017 05:21:58 +0200	[thread overview]
Message-ID: <20170531032207.95830-1-luc.vanoostenryck@gmail.com> (raw)
The goal of this series is to add the 'division by zero'
warnings that are missing. Indeed, sparse only warned about
division by zero when the LHS was a constant. When the LHS
was not a constant (and thus also when the division was part
of a compound assignement) no warning was ever issued.
Note: the floating point division need a similar changes
      which will be part of another series.
This series is also available in the git repository at:
  git://github.com/lucvoo/sparse.git div-by-zero
Luc Van Oostenryck (9):
  add is_pseudo_value()
  add a .warned field to struct instruction
  div0: warn on integer divide by 0 also when the lhs is not constant
  div0: warn on division by zero - general case
  div0: add warning option -Wdiv-by-zero
  div0: use -Wdiv-by-zero
  div0: warn also during simplification
  div0: warn on float divide by 0 also when the lhs is not constant
  div0: add missing tests for floating point div by zero
 expand.c                    | 30 +++++++++++-------------
 lib.c                       |  2 ++
 lib.h                       |  1 +
 linearize.c                 | 20 ++++++++++++++++
 linearize.h                 | 12 ++++++++--
 simplify.c                  | 12 ++++++++++
 validation/div-by-zero-fp.c | 24 +++++++++++++++++++
 validation/div-by-zero.c    | 57 +++++++++++++++++++++++++++++++++++++++++++++
 8 files changed, 140 insertions(+), 18 deletions(-)
 create mode 100644 validation/div-by-zero-fp.c
 create mode 100644 validation/div-by-zero.c
-- 
2.13.0
next             reply	other threads:[~2017-05-31  3:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31  3:21 Luc Van Oostenryck [this message]
2017-05-31  3:21 ` [PATCH 1/9] add is_pseudo_value() Luc Van Oostenryck
2017-05-31  3:22 ` [PATCH 2/9] add a .warned field to struct instruction Luc Van Oostenryck
2017-05-31  3:22 ` [PATCH 3/9] div0: warn on integer divide by 0 also when the lhs is not constant Luc Van Oostenryck
2017-05-31  3:22 ` [PATCH 4/9] div0: warn on division by zero - general case Luc Van Oostenryck
2017-05-31  3:22 ` [PATCH 5/9] div0: add warning option -Wdiv-by-zero Luc Van Oostenryck
2017-05-31  3:22 ` [PATCH 6/9] div0: use -Wdiv-by-zero Luc Van Oostenryck
2017-05-31  3:22 ` [PATCH 7/9] div0: warn also during simplification Luc Van Oostenryck
2017-05-31  3:22 ` [PATCH 8/9] div0: warn on float divide by 0 also when the lhs is not constant Luc Van Oostenryck
2017-05-31  3:22 ` [PATCH 9/9] div0: add missing tests for floating point div by zero 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=20170531032207.95830-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).