Thomas Daede

Is this a regression? (is this problem new with 0.5.0?)

about a 0.04% loss https://beta.arewecompressedyet.com/?job=interpfilter-2019-08-09_175924-f3c43a4&job=master-ec0c7787dd1598f4cecaedda2a120ff4ab0eb6d0

going to actually stack all of the interpfilter commits here before landing

No, there is no desync.

@ycho I will look at it a bit today, but if I don't find a fix I'd appreciate it if you could also look.

Should probably use the `install` binary rather than cp to get proper permissions set. There's also an incantation of cargo cinstall that I managed to install directly with, I can...

Hmm, this seems like an internal linking error, like a file got corrupted or a symbol got too long. Do you know if this happens for the 64 bit target...

This might be intentional as a way to avoid false dependencies "for free". That said, it obviously isn't actually free. Might be worth checking if the common places were this...

OK, I missed it was still VEX coded. I think patching x86inc.asm (and sending a patch upstream if desired) makes the most sense. I can't think of any other side...

Really old pr... but this needs to pass appveyor first.