All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Possible incorrect linearization of code (master branch)
Date: Tue, 7 Mar 2017 23:45:11 +0800	[thread overview]
Message-ID: <CANeU7Qm4fYeTeiN61dCSgSGHTUNCjLGtjdJmBVbxXKu7cC_OPw@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxexwB_krnNULmiGMCySoaVqx1Q+KiuE_tPS7P59nT7giA@mail.gmail.com>

On Tue, Mar 7, 2017 at 6:39 AM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:

> As I mentioned before I am using Sparse to create a JIT compiler for
> C. So this needs to be callable as a library - and I need the ability
> to call it many times. Moreover it must be possible to call several
> instances of Sparse simultaneously without conflict. To achieve all
> this, all global state is held in a set of structures. The main change
> is that the most function calls have an additional argument. The other

Adding an additional argument is a very big change.


> changes are related to initialization of the various global structures
> used by Sparse.

In your usage case, is it possible to use some kind of lock to avoid
racing to initialize sparse?

> Generally I try to keep the code as far as possible
> identical to Sparse except for these changes. Even so merging is very
> painful.

May be need a script of some short to automate part of the change.

Do you have that big and painful change already?

Chris

  parent reply	other threads:[~2017-03-07 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 15:22 Possible incorrect linearization of code (master branch) Dibyendu Majumdar
2017-03-06 16:36 ` Luc Van Oostenryck
2017-03-06 18:47   ` Dibyendu Majumdar
2017-03-06 19:26     ` Luc Van Oostenryck
2017-03-06 22:39       ` Dibyendu Majumdar
2017-03-07  6:42         ` Luc Van Oostenryck
2017-03-07 15:45         ` Christopher Li [this message]
2017-03-07 17:13           ` Dibyendu Majumdar

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=CANeU7Qm4fYeTeiN61dCSgSGHTUNCjLGtjdJmBVbxXKu7cC_OPw@mail.gmail.com \
    --to=sparse@chrisli.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=mobile@majumdar.org.uk \
    /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.