On Fri, 19 Dec 2014 09:52:26 +0000
Paul Moore <p.f.moore@gmail.com> wrote:
> On 19 December 2014 at 08:26, Maciej Fijalkowski <fijall@gmail.com> wrote:
> > I would like to add that "not doing anything" is not a good strategy
> > either, because you accumulate bugs that get fixed upstream (I'm
> > pretty sure all the problems from cpython got fixed in upstream
> > libffi, but not all libffi fixes made it to cpython).
>
> Probably the easiest way of moving this forward would be for someone
> to identify the CPython-specific patches in the current version, and
> check if they are addressed in the latest libffi version. They haven't
> been applied as they are, I gather, but maybe equivalent fixes have
> been made. I've no idea how easy that would be (presumably not
> trivial, or someone would already have done it). If the patches aren't
> needed any more, upgrading becomes a lot more plausible.

Another strategy is to dump our private fork, link with upstream
instead, and see what breaks.
Presumably, our test suite should be able to catch some (most?) of that
breakage.