diff options
| author | Alex Crichton <alex@alexcrichton.com> | 2017-03-23 15:46:40 -0700 |
|---|---|---|
| committer | Alex Crichton <alex@alexcrichton.com> | 2017-03-24 09:59:18 -0700 |
| commit | e6e8c919613615d2e296e5a4adbe81c57c0dbce9 (patch) | |
| tree | bca2bc918626e84fcc28fa4be6142d205613b4a9 /src/test/run-pass/thinlto | |
| parent | d5580374d7eb8795a8188be4650bd5079a25c6b3 (diff) | |
| download | rust-e6e8c919613615d2e296e5a4adbe81c57c0dbce9.tar.gz rust-e6e8c919613615d2e296e5a4adbe81c57c0dbce9.zip | |
appveyor: Upgrade MinGW toolchains we use
In debugging #40546 I was able to reproduce locally finally using the literal toolchain that the bots were using. I reproduced the error maybe 4 in 10 builds. I also have the 6.3.0 toolchain installed through `pacman` which has yet to have a failed build. When attempting to reproduce the bug with the toolchain that this commit switches to I was unable to reproduce anything after a few builds. I have no idea what the original problem was, but I'm hoping that it was just some random bug fixed somewhere along the way. I don't currently know of a technical reason to stick to the 4.9.2 toolchains we were previously using. Historcal 5.3.* toolchains would cause llvm to segfault (maybe a miscompile?) but this seems to have been fixed recently. To me if it passes CI then I think we're good. Closes #40546
Diffstat (limited to 'src/test/run-pass/thinlto')
0 files changed, 0 insertions, 0 deletions