linux-sparse.vger.kernel.org archive mirror
 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 v2 0/2] fix: give a type to bad conditionnal expressions
Date: Fri,  4 Aug 2017 18:06:20 +0200	[thread overview]
Message-ID: <20170804160622.18260-1-luc.vanoostenryck@gmail.com> (raw)

The goal of this series is to fix the slow compilation of
the Wine test file.

It should be safe enough but IMO it's not -rc5 material.


This series is available in the git repository at:

  git://github.com/lucvoo/sparse.git fix-type-bad-cond-expr-v2

for you to fetch changes up to be35da05f38df984d518bc4670b36aa0b7ad4185:

  fix: give a type to bad cond expr with known condition (2017-08-04 15:49:49 +0200)

----------------------------------------------------------------
Luc Van Oostenryck (2):
      take comma expr in account for constant value
      fix: give a type to bad cond expr with known condition

 evaluate.c                   | 12 ++++++++++++
 expand.c                     | 30 ++++++++++++++++++++++++++++++
 expression.h                 |  1 +
 validation/cond-err-expand.c | 27 +++++++++++++++++++++++++++
 4 files changed, 70 insertions(+)
 create mode 100644 validation/cond-err-expand.c

             reply	other threads:[~2017-08-04 16:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 16:06 Luc Van Oostenryck [this message]
2017-08-04 16:06 ` [PATCH v2 1/2] take comma expr in account for constant value Luc Van Oostenryck
2017-08-04 19:49   ` Christopher Li
2017-08-04 20:27     ` Luc Van Oostenryck
2017-08-04 21:05       ` Christopher Li
2017-08-04 21:20         ` Luc Van Oostenryck
2017-08-05 12:02           ` Christopher Li
2017-08-04 16:06 ` [PATCH v2 2/2] fix: give a type to bad cond expr with known condition Luc Van Oostenryck
2017-08-04 19:50   ` Christopher Li

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=20170804160622.18260-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 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).