News for hackers. Stuff that matters.

A comment on GCC Rust: GCC Front-End for Rust. Parent comment

Re:GCC Rust: GCC Front-End for Rust by bonzini on Sunday January 10, 2021 @01:40PM (#25717906)
A compiler front-end is pretty boring software in terms of memory safety. Lots of things that the front-end allocates are simply never freed.

Have you ever seen GCC crash with a SIGSEGV? I rarely did even when I used to be a GCC developer.

[ Parent | on HN ]
Re:GCC Rust: GCC Front-End for Rust by pm215 on Sunday January 10, 2021 @02:06PM (#25718301)
Indeed. Notoriously, a SEGV in gcc during compilation used to usually mean "your hardware is flaky": https://tldp.org/FAQ/sig11/html/index.html
[ Parent | on HN ]
Re:GCC Rust: GCC Front-End for Rust by zzz11 on Sunday January 10, 2021 @06:36PM (#25721647)
That was before the invention of fuzzing.
[ Parent | on HN ]
Re:GCC Rust: GCC Front-End for Rust by jjnoakes on Sunday January 10, 2021 @05:39PM (#25720937)
There are still out-of-bounds concerns and chasing through NULL pointers. (Not arguing against gcc's quality or stability, just listing memory safety concerns that transcend memory deallocation)
[ Parent | on HN ]