News for hackers. Stuff that matters.
Re:Achievement unlocked: rustc segfault by rurban on Sunday April 10, 2022 @05:21PM (#30981831)
Pretty easy to get llvm segfaults, I got that with pony also in development versions. The difference to rust is that this happens with rust compiled binaries also at run-time, in pony very rarely.

https://github.com/rust-lang/rust/issues?q=is%3Aissue+SIGSEG... => 87 + 291

vs https://github.com/ponylang/ponyc/issues?q=is%3Aissue+SIGSEG... => 11 + 50

Now compare that to a safe systems language, e.g. sbcl: https://bugs.launchpad.net/sbcl/+bugs?field.searchtext=SIGSE... => 1 (invalid)

or clisp: https://sourceforge.net/p/clisp/bugs/?q=%7B%22status%22%3A+%... => 15

Re:Achievement unlocked: rustc segfault by woodruffw on Sunday April 10, 2022 @05:25PM (#30981874)
Not to besmirch Pony (I think it's a very interesting language), but isn't some of this a base sampling error? There are probably a few orders of magnitude more engineers writing Rust (and therefore running `rustc`), so we'd expect crashes in Rust to surface more frequently.
Re:Achievement unlocked: rustc segfault by rurban on Sunday April 10, 2022 @05:30PM (#30981910)
Not in memory safe languages, sorry.
Re:Achievement unlocked: rustc segfault by woodruffw on Sunday April 10, 2022 @05:33PM (#30981937)
I'm not sure I understand. Rust is memory safe, and the memory unsafety happening here isn't in Rust itself: an IR generation bug in Rust is causing memory unsafety in LLVM, which is written in C++.

(Besides: If GitHub's stats are correct, `ponyc` seems to be >60% C and C++?)

Re:Achievement unlocked: rustc segfault by saghm on Sunday April 10, 2022 @08:27PM (#30983206)
Compilers for memory-safe languages can't have bugs in them?
Re:Achievement unlocked: rustc segfault by 3836293648 on Monday April 11, 2022 @07:59AM (#30987489)
Compilers for memory safe languages written in the same memory safe languages should be expected to have to same guarantees as any other program written in that language
Re:Achievement unlocked: rustc segfault by UncleEntity on Monday April 11, 2022 @10:32AM (#30989286)
I think that’s the fifth Futamura projection — compiling a compiler with itself cancels out bugs.
Re:Achievement unlocked: rustc segfault by gpm on Sunday April 10, 2022 @05:38PM (#30981982)
> The difference to rust is that this happens with rust compiled binaries also at run-time,

The list of issues you linked in an apparent attempt to support this claim are almost all (or maybe even all) compile time crashes not runtime crashes...

Re:Achievement unlocked: rustc segfault by kjeetgill on Sunday April 10, 2022 @05:58PM (#30982138)
The post is also about crashes in rustc not crashes in rust programs, right?
Re:Achievement unlocked: rustc segfault by gpm on Sunday April 10, 2022 @06:05PM (#30982188)
The top level link, yes.

The comment I replied to... I quoted the text that made me think it wasn't. Am I misinterpreting it?

Re:Achievement unlocked: rustc segfault by ergl on Monday April 11, 2022 @07:36AM (#30987302)
Pony committer here, I don't think this comparison is very fair, Rust has way more users, and thus way more eyes looking at it and reporting bugs. We've also had a few runtime segfauts before due to LLVM (mainly when porting to new platforms, like Apple's M1), and we try hard to fix them when we find them.