linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Michael Stefaniuc <mstefani@mykolab.com>,
	Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: Infinite loop with OOM while testing Sparse on Wine code
Date: Wed, 19 Jul 2017 22:43:01 +0200	[thread overview]
Message-ID: <CAExDi1Quxc_ZfmdW2-kY=Q312Dnbi_7OsRX85_uGrHWTk1vtpw@mail.gmail.com> (raw)
In-Reply-To: <CANeU7Qkm_V8cYW3yKKBHo6PY9r0CA+XoTfJCVZbcOS14Am_PiA@mail.gmail.com>

> Luc, do you have time to take a look at this? Without your input,
> RC5 will be released with commit  11b1a83b disabled.

I'm not yet fully back but I'll be able to look at it later, probably
tomorrow (it's already evening here).

-- Luc

  parent reply	other threads:[~2017-07-19 20:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 14:47 Infinite loop with OOM while testing Sparse on Wine code Michael Stefaniuc
2017-07-18 15:11 ` Christopher Li
2017-07-18 17:11 ` Christopher Li
2017-07-18 23:12 ` Christopher Li
2017-07-19  0:07   ` Christopher Li
2017-07-19 13:26     ` Christopher Li
2017-07-19 15:25       ` Christopher Li
2017-07-19 18:50         ` Michael Stefaniuc
2017-07-19 20:43       ` Luc Van Oostenryck [this message]
2017-07-19 21:16         ` Christopher Li
2017-07-20 22:44           ` Luc Van Oostenryck
2017-07-26 17:29             ` Christopher Li
2017-07-29 14:39       ` Luc Van Oostenryck
2017-07-29 20:05         ` Christopher Li
2017-07-29 23:38       ` Luc Van Oostenryck
2017-07-29 23:58         ` [PATCH] fix: try_to_simplify_bb eargerness part 2 Luc Van Oostenryck
2017-07-30 15:38           ` Christopher Li
2017-07-30 16:04             ` Luc Van Oostenryck
2017-07-30 17:06               ` Christopher Li
2017-07-30  0:01         ` Infinite loop with OOM while testing Sparse on Wine code 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='CAExDi1Quxc_ZfmdW2-kY=Q312Dnbi_7OsRX85_uGrHWTk1vtpw@mail.gmail.com' \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=mstefani@mykolab.com \
    --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).