| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Reproducible-BUILD_PATH_PREFIX_MAP.patch | Reproducible BUILD_PATH_PREFIX_MAP Make builds reproducible by honoring BUILD_PATH_PREFIX_MAP Upstream has rejected the patch in this form and promised to implement an alternative they are happy with instead. That hasn't happened yet though. |
Michael Stapelberg <stapelberg@debian.org> | yes | upstream | 2018-02-08 | |
| 0002-Fix-Lintian-warnings-about-wrong-interpreter-path.patch | Fix Lintian warnings about wrong interpreter path The command used for this change is as follows: grep -rH "/usr/bin/env perl" * | cut -d: -f1 | xargs -n1 sed -i -e "s,/usr/bin/env perl,/usr/bin/perl," |
"Dr. Tobias Quathamer" <toddy@debian.org> | no | 2018-12-19 | ||
| 0003-arm64-arm64asm-recognise-new-ssbb-pssbb-mnemonics-fr.patch | arm64/arm64asm: recognise new ssbb/pssbb mnemonics from objdump Fixes golang/go#27754 |
Michael Hudson-Doyle <michael.hudson@canonical.com> | no | 2018-09-20 | ||
| 0004-fix-Fstatat-by-using-fillStat_t-on-linux-mips64x.patch | [PATCH] unix: fix Fstatat by using fillStat_t on linux/mips64x The stat structure on linux/mips64x differ between C library and the kernel, as described in the stat(2) man page. Fstat, Lstat and Stat on linux/mips64x already converts the stat structure using a fillStat_t function, very similar to __xstat_conv in GLIBC. Doing the same for Fstatat before calling SYS_NEWFSTATAT fixes the "Fstatat: returned stat does not match Stat/Lstat" error in TestFstatat. Fixes golang/go#29401 |
Anthony Fok <foka@debian.org> | no | 2018-12-28 | ||
| 0005-fix-MIPS-SGTconst-with-shift-rules.patch | [PATCH] cmd/compile: fix MIPS SGTconst-with-shift rules (SGTconst [c] (SRLconst _ [d])) && 0 <= int32(c) && uint32(d) <= 31 && 1<<(32-uint32(d)) <= int32(c) -> (MOVWconst [1]) This rule is problematic. 1<<(32-uint32(d)) <= int32(c) meant to say that it is true if c is greater than the largest possible value of the right shift. But when d==1, 1<<(32-1) is negative and results in the wrong comparison. Rewrite the rules in a more direct way. Fixes #29402. |
Cherry Zhang <cherryyz@google.com> | no | 2018-12-25 |