Bug#842956: llvm-3.9-dev: Please backport 279980 since rustc 1.12.1 needs it
infinity0 at debian.org
Thu Nov 3 17:52:00 UTC 2016
> Le 03/11/2016 à 18:04, Ximin Luo a écrit :
>> Ximin Luo:
>>> rust.git$ git format-patch 4105790 # 4105790 and earlier are already applied to our LLVM
>>> In 1:3.9-4 you applied 0013, and this bug report is me asking you to apply
>>> 0011. However if these two don't make our rustc work, then the heavy-handed
>>> approach would be to apply all of the above patches. I've tested that these
>>> apply cleanly to our LLVM 1:3.9-4, but not yet built the thing.
>> TL;DR: we should probably apply 14-17. None of these are critical, but sound fairly important or helpful, and might save us from getting weird errors elsewhere.
>> The rest are "nice to have" but not essential if you want to keep the package as close to upstream as possible.
> If they are not essential, I won't take them in Debian. I don't want to diverge too much, especially as they are also published on llvm.org/apt/
> If you care about these patches, you should report bug Upstream (LLVM) to see them merged for 3.9.1 (we are working on it currently)
On further research, 14 is not necessary at this time: https://github.com/rust-lang/rust/issues/36356
The others seem more important, but also have already been applied upstream:
15 is LLVM r283517
The issue description says "Windows" but a later comment from a rust contributor says "Patch appears to fix problem (on Linux at least)" implying that they experienced it on Linux too.
16 is LLVM r282506
17 is LLVM r282611
OOM after using 18GB of memory, I'm pretty sure "Release mode with debug info" applies to us.
Not sure if they have been applied to the 3.9.1 branch. I can check this when I next have more time, or perhaps you agree it's OK to backport them if they're already applied to trunk?
More information about the Pkg-llvm-team