-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Nested clean-up-requiring blocks in loop (sometimes) segfault [rustc] #293
Comments
Here's a simpler case, no segfault, but corrupted memory EDIT: bogus snippet that didn't reproduce the issue removed |
That case makes sense, due to +=. But this one also crashes:
I'll look closer once I'm in the office. Probably something that will jump out given a .dot CFG. |
I can't reproduce the crash with either snippet. Does anyone think this problem still exists? |
The compiler has changed a lot in the meantime. I guess this was fixed at some point. |
…crichton Add the TIOCGWINSZ and TIOCSWINSZ constants I've added the `TIOCGWINSZ` and `TIOCSWINSZ` constants/ioctl control codes. I wasn't quite sure where to put them, so hopefully they're in the right place. As of now it's set to compile on 'FreeBSD-like' platforms, so it will compile on both FreeBSD *and* DragonflyBSD. I've only tested it on FreeBSD though, but it should also work on DragonflyBSD AFAIK. Fixes rust-lang#292.
I believe we're reserving the `simd` module for exclusively the portable types and their operations, so this commit moves the various x86-specific types from the portable modules to the `x86` module. Along the way this also adds some doc blocks for all the existing x86 types.
This one does:
The text was updated successfully, but these errors were encountered: