From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: linux-sparse@vger.kernel.org, Christopher Li <sparse@chrisli.org>
Subject: Re: [PATCH v6 00/15] prepare for LLVM fixes
Date: Tue, 28 Mar 2017 00:22:13 +0200	[thread overview]
Message-ID: <20170327222212.jle5tzjevfsigvuw@macpro.local> (raw)
In-Reply-To: <7406f777-5e8b-5ae0-55e0-26a36ddb64b5@ramsayjones.plus.com>
On Mon, Mar 27, 2017 at 10:56:52PM +0100, Ramsay Jones wrote:
> 
> 
> On 27/03/17 18:33, Luc Van Oostenryck wrote:
> > This serie contains preparatory patches for
> > sparse-llvm's fixes but not sparse-llvm specific
> > and having some values of their own.
> > 
> > These patches were extracted from a previous
> > serie containing also the sparse-llvm patches.
> > 
> > Changes since v5:
> > - use a table for compare_opcode() & swap_compare_opcode()
> > - fix test cases on 32bit machines
> 
> Hmm, I assumed that this series should apply to master, and then
> the following 52 patch series on top.
Well no, sorry.
I haven't explained because I thought it was obvious but
of course, it's not obvious at all.
These series apply, and in general any patches or series I send,
in the order I send them, on top of the stable part of sparse-next.
And by "the stable part of sparse-next" I mean that if sparse-next
contains serie-xyz-v2 and I sent serie-xyz-v3, the serie will apply
at the same place that the -v2 serie was.
It's a time somehow painfull, I agree. It's why I try also push
the serie on github when the serie is worth of it (and complete).
in this case you can find everything at:
	https://github.com/lucvoo/sparse/commits/llvm-fixes-v6
(and yes, this tree contains a few more patches, not in the serie
already submitted but not yet in sparse-next).
Sorry for any lost of time.
-- Luc
next prev parent reply	other threads:[~2017-03-27 22:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 17:33 [PATCH v6 00/15] prepare for LLVM fixes Luc Van Oostenryck
2017-03-27 17:33 ` [PATCH v6 01/15] don't output value of anonymous symbol's pointer Luc Van Oostenryck
2017-03-27 17:33 ` [PATCH v6 02/15] add table to "negate" some opcode Luc Van Oostenryck
2017-03-31 10:30   ` Christopher Li
2017-03-31 19:18     ` Luc Van Oostenryck
2017-03-27 17:33 ` [PATCH v6 03/15] use opcode table for compare_opcode() Luc Van Oostenryck
2017-03-27 17:33 ` [PATCH v6 04/15] canonicalize binops before simplification Luc Van Oostenryck
2017-03-27 17:33 ` [PATCH v6 05/15] canonicalize compare instructions Luc Van Oostenryck
2017-03-27 17:33 ` [PATCH v6 06/15] add is_signed_type() Luc Van Oostenryck
2017-03-27 17:33 ` [PATCH v6 07/15] fix usage of inlined calls Luc Van Oostenryck
2017-03-27 17:33 ` [PATCH v6 08/15] inlined calls should not block BB packing Luc Van Oostenryck
2017-03-27 17:33 ` [PATCH v6 09/15] give function's arguments a type via OP_PUSH Luc Van Oostenryck
2017-03-27 17:34 ` [PATCH v6 10/15] insure that all OP_PUSHs are just before their OP_CALL Luc Van Oostenryck
2017-03-27 17:34 ` [PATCH v6 11/15] give a type to OP_PHISOURCEs Luc Van Oostenryck
2017-03-27 17:34 ` [PATCH v6 12/15] give a type to OP_SELs, always Luc Van Oostenryck
2017-03-27 17:34 ` [PATCH v6 13/15] give a type to OP_SWITCHs Luc Van Oostenryck
2017-03-27 17:34 ` [PATCH v6 14/15] add doc about sparse's instructions/IR Luc Van Oostenryck
2017-03-27 17:34 ` [PATCH v6 15/15] add support for wider type in switch-case Luc Van Oostenryck
2017-03-27 21:56 ` [PATCH v6 00/15] prepare for LLVM fixes Ramsay Jones
2017-03-27 22:22   ` Luc Van Oostenryck [this message]
2017-03-28 16:01     ` Ramsay Jones
2017-03-28 18:10     ` Linus Torvalds
2017-03-31  4:49       ` Christopher Li
2017-03-31  9:25         ` Luc Van Oostenryck
2017-03-31 10:04           ` Christopher Li
2017-03-31 12:19             ` Luc Van Oostenryck
2017-03-31 12:22               ` Dibyendu Majumdar
2017-03-31 12:24                 ` Dibyendu Majumdar
2017-03-31 15:42               ` Christopher Li
2017-03-31  9:26         ` Christopher Li
2017-04-01 10:49 ` [GIT PULL v6] " 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=20170327222212.jle5tzjevfsigvuw@macpro.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=ramsay@ramsayjones.plus.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).