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: Linus Torvalds <torvalds@linux-foundation.org>,
	Christopher Li <sparse@chrisli.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/4] phisrc fixes
Date: Wed,  4 Jan 2017 04:03:17 +0100	[thread overview]
Message-ID: <20170104030321.28019-1-luc.vanoostenryck@gmail.com> (raw)

This series fixes problems with the creation and placement of phisrcs.

Patch 1 is a preparatory step for patch 4 but fixes a very problem
of its own.
Patch 2 & 3 are the main fixes.
Patch 4 is a small improvement but also avoid divergence in the code
regarding the changes made in patch 3.

Note: I'm very sure there is still others bugs in the same corner but
      at least these patch improve the situation a bit.
Note: Only one patch has a regression test. For the other 3, it's
      to have some examples but this doesn't fit very well into the current
      testsuite.
      
This serie can also be found on the 'sent/broken-phisrc' of
	git://github.com/lucvoo/sparse.git

Luc Van Oostenryck (4):
  volatile loads must not be simplified
  fix superfluous phisrc
  fix phisrc mixup
  missing load simplification

 flow.c                       | 23 ++++++++++++++++-------
 memops.c                     | 13 ++++++-------
 validation/memops-volatile.c | 21 +++++++++++++++++++++
 3 files changed, 43 insertions(+), 14 deletions(-)
 create mode 100644 validation/memops-volatile.c

             reply	other threads:[~2017-01-04  3:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  3:03 Luc Van Oostenryck [this message]
2017-01-04  3:03 ` [PATCH 1/4] volatile loads must not be simplified Luc Van Oostenryck
2017-01-04  3:03 ` [PATCH 2/4] fix superfluous phisrc Luc Van Oostenryck
2017-01-04  3:03 ` [PATCH 3/4] fix phisrc mixup Luc Van Oostenryck
2017-01-04  3:03 ` [PATCH 4/4] missing load simplification 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=20170104030321.28019-1-luc.vanoostenryck@gmail.com \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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).