This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/67466] Project segfaulting, working with other compilers
- From: "morandidodo at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 12 Sep 2016 13:19:36 +0000
- Subject: [Bug c++/67466] Project segfaulting, working with other compilers
- Auto-submitted: auto-generated
- References: <bug-67466-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67466
morandidodo at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |6.2.1
Known to fail| |5.2.0
--- Comment #2 from morandidodo at gmail dot com ---
I am sorry, but it has been more than an year and now I am using GCC 6.2.1, I
am not able to reproduce the bug anymore. Indeed, the new version seems to work
flawlessly, and I do not get segfaults even with the address sanitizer.
If someone have the 5.x branch installed, the Voxelands commit which caused the
problem was the fa519dee2751b46ee36f4443d5b194dbbe1dd1e5.
Otherwise, I could close the issue. I do not know if it is worth to track down
strange and uncommon issues with an old version of the compiler...