From: Christopher Li <sparse@chrisli.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
Dibyendu Majumdar <mobile@majumdar.org.uk>
Subject: Re: [PATCH 0/3] assorted LLVM fixes
Date: Mon, 14 Aug 2017 16:21:50 -0400 [thread overview]
Message-ID: <CANeU7Qmbs9FZqw1ZNRY7=ZyDjuL3OWMMyjeO_cUBRzpb-=wBbA@mail.gmail.com> (raw)
In-Reply-To: <20170814194152.36289-1-luc.vanoostenryck@gmail.com>
On Mon, Aug 14, 2017 at 3:41 PM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> This series contains two fixes for sparse-llvm.
> It is supposed to be applied on top of all others
> LLVM fixes.
>
I think we are going to have the finial release of 0.5.1 this
Wednesday if no show stoppers.
Can you resend your other LLVM fixes (this patches are depend
on) after the release? I can even have a temporary branch
to merge those right now.
We can do a quick fix up of 0.5.2 the problem we know so
far.
Make it reasonable stable and cut another release.
Chris
next prev parent reply other threads:[~2017-08-14 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 19:41 [PATCH 0/3] assorted LLVM fixes Luc Van Oostenryck
2017-08-14 19:41 ` [PATCH 1/2] llvm: warn instead of assert on global inits Luc Van Oostenryck
2017-08-14 19:41 ` [PATCH 2/2] llvm: add support for float initializer Luc Van Oostenryck
2017-08-14 19:41 ` [PATCH 3/3] llvm: only compare void pointers Luc Van Oostenryck
2017-08-14 20:21 ` Christopher Li [this message]
2017-08-14 20:29 ` [PATCH 0/3] assorted LLVM fixes Luc Van Oostenryck
2017-08-14 20:31 ` Christopher Li
2017-08-14 23:56 ` Dibyendu Majumdar
2017-08-15 0:42 ` Christopher Li
2017-08-14 21:23 ` Ramsay Jones
2017-08-15 0:39 ` 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='CANeU7Qmbs9FZqw1ZNRY7=ZyDjuL3OWMMyjeO_cUBRzpb-=wBbA@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 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).