diff options
| author | bors <bors@rust-lang.org> | 2017-03-24 18:40:57 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2017-03-24 18:40:57 +0000 |
| commit | 8cf8fc9d8973a4d523c01dcba2ef991e0f2393d7 (patch) | |
| tree | 50b32ac68040149cc2d5b9d125dc36f1a94479c6 /src/libstd/process.rs | |
| parent | f2036c7be4e783f459d1f9a712c5a7b3ef6679bd (diff) | |
| parent | e6e8c919613615d2e296e5a4adbe81c57c0dbce9 (diff) | |
| download | rust-8cf8fc9d8973a4d523c01dcba2ef991e0f2393d7.tar.gz rust-8cf8fc9d8973a4d523c01dcba2ef991e0f2393d7.zip | |
Auto merge of #40777 - alexcrichton:update-mingw-compilers, r=aturon
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/libstd/process.rs')
0 files changed, 0 insertions, 0 deletions