-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compiler bug with cyclic weak references on Windows #30658
Comments
It appears that this bug is not restricted to Windows. I have attached a small tarball of a project that fails (inappropriately?) when running |
Interestingly enough, the same issue does not occur with |
Works fine on Windows-gnu, I cannot test msvc. @rustbot modify labels: -O-windows +O-windows-msvc |
The issue was fixed in version 1.19, most likely by #42225. I reproduced it in version 1.5, 1.10, 1.17, and 1.18 but not 1.19. Can someone please close this issue? I don't have permissions. |
Should we add a test? |
It looks like there is more than one issue. The arithmetic overflow error was fixed in 1.6.0. I got a linking error because I was using the GNU linker and that didn't work until 1.19.0. The linker error I got was different. I can't reproduce the original linker error in x86_x64 Cross Tools Command Prompt for VS 2019 which uses the Microsoft linker. I don't know if a test is needed for this. |
I've tracked down the following bug on 1.5 stable. It only appears to happen on Windows, as I've tried the same program on Linux x64 without problems:
test.rs
:On Linux, I get the expected result:
On Windows, this fails during compilation:
I first identified this bug while writing something as part of my ray tracer. It failed to run a fairly simple unit test using
cargo test
. The result for that was:However, the weird thing is that this only shows up in the library if I change the definition of
SDFace
toThis seems like a bug somewhere, but I don't know where -- if I need to analyze anything additionally, please let me know.
The text was updated successfully, but these errors were encountered: