segfault while compiling stage2 libsyntax for i686-pc-windows-gnu #28260
Comments
steveklabnik
added
I-ICE
|
I've reported this as an LLVM bug: https://llvm.org/bugs/show_bug.cgi?id=24722 |
|
Closing as a duplicate of #28962 |
|
Er actually this has a smaller number, gonna go in favor of this. |
|
Also so this shows up in github search: gcc 5.2 fails to build LLVM successfully on MinGW as it segfaults at runtime |
…chton This PR adds a note to the end of the Windows build instructions to reflect the issues detailed in #28260, as well as a work around using older versions of gcc. I've avoided going into detail as I did not wish to bloat the README, and so that the changes are easy to yank once the issue is resolved.
|
This should be fixed in GCC 6, I believe - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66655 |
|
I have indications that GCC 5.3 also works, but I didn't have time to fully test. If someone has a windows box and wants to try it... :) |
|
@taralx |
|
I did indeed test without them. Thanks for the heads up. |
|
Testing today, it appears that master branch builds fine with gcc 5.4.0. I suspect we fixed this "by accident" when we updated LLVM at some point |
configure: Check for valid Python on MinGW as well The LLVM build system is somewhat picky about which Python is used to build it as it's known to be incompatible with the default `python2` package that ships with MinGW. This was previously detected for MSVC builds but the logic was left out for MinGW by accident (now that we've switched to cmake builds for LLVM everywhere). This corrects the `./configure` check and also updates the `README.md` accordingly. Additionally, a number of instructions were updated to work with the most recent copy of MSYS2. Closes #28260 Closes #34489
@alexcrichton has indicated this may be related to using newer versions of gcc, which might explain why it doesn't fail on the buildbot machines.
The segfault occurs while running the
tailcallelimllvm pass onast::Pat_::drop(), possibly during the prerequisitettianalysis.Turning on any kind of debug information for either rust or llvm causes the problem to disappear.
The text was updated successfully, but these errors were encountered: