News for hackers. Stuff that matters.
Re:Achievement unlocked: rustc segfault by VWWHFSfQ on Sunday April 10, 2022 @08:08PM (#30983093)
This doesn't seem like a bug in rustc at all. Maybe just by emitting bad IR. But this is actually bug in LLVM.
Re:Achievement unlocked: rustc segfault by tsimionescu on Monday April 11, 2022 @01:32AM (#30985029)
No, LLVM is configured by rustc to NOT to check its input (for performance reasons), so it's normal for it to crash if fed invalid input. The bug is 100% in rustc's court.
Re:Achievement unlocked: rustc segfault by woodruffw on Sunday April 10, 2022 @09:15PM (#30983473)
I think it's reasonable to consider it a bug in both: it's a MIR lowering bug, one that gets promoted into a different bug by LLVM.
Re:Achievement unlocked: rustc segfault by DannyBee on Sunday April 10, 2022 @08:13PM (#30983125)
why? They are using a build with assertions/etc disabled, so it segfaults rather than asserts. When you use a build that is set not to do that, it gives you an error :)
Re:Achievement unlocked: rustc segfault by LAC-Tech on Sunday April 10, 2022 @09:27PM (#30983537)
If rustc uses a dependency that has a bug and this manifests itself as a bug in rustc, then IMO rustc still has a bug.