5 ms·
That's not related to C, except in the sense that GCC is written in C. GCC was just emitting incorrect code because it had a bug in its code generator. If the
by kragen 5y ago
That's not related to C, except in the sense that GCC is written in C. GCC was just emitting incorrect code because it had a bug in its code generator. If there's a bug in the LLVM code generator (which is written in C++), rustc might end up doing the same thing.
If you write the compiler in Rust it could still happen. Rust code (that compiles) has less bugs than the corresponding C but not zero bugs.
It doesn't sound like you went overboard, it sounds like a good project. Maybe you should have written it in Perl 5.001 though.
- charcircuit 5y agoGCC is written in C++
- kragen 5y agoThere are small parts of GCC that are written in C++, but at the time when universities had "one multi-user unix server for all students" it was 100% C.
- turminal 5y agoand there was no LLVM :)
- kragen 5y agoNor Rust!
- pjmlp 5y agoYeah, but that was 40 years ago, back when GCC still stood for GNU C Compiler.
- kragen 5y agoI had pegged it as between 20 and 30 years ago, but someone pointed out that the author said they tried using asan. 40 years ago most universities didn't have Unix boxes accessible to random undergraduates at all. GCC started having parts written in C++ 12 years ago: https://lwn.net/Articles/542457/ https://lwn.net/Articles/542457/
- infogulch 5y agoBecause it was C I couldn't be sure it was the compiler's fault until I really exhausted every other option. Maybe spent 100h between a few people getting to the end of it. If I had written in safe Rust (I would have, I wasn't doing anything weird) and it segfaulted I'd know immediately that the compiler was the problem because you can't make safe rust segfault.
- kragen 5y agoYes, that's true.
- andrewchambers 5y agoOr he could do the normal thing and run valgrind to instantly see exactly where the problem is. I don't even disagree with the premise, but these are straw man arguments.
- kragen 5y agoValgrind didn't exist then. (Next you're going to say ASan and UBSan. Those didn't exist either.) They (he?) could have run GDB and disassembled the code around the crashing instruction and verified that the machine code there didn't make any fucking sense. But that implies they knew assembly language well enough to recognize when their compiler was spewing nonsense, which is a couple of steps above "can read working assembly emitted by the compiler" or even "can write applications in assembly language". Even with Valgrind it can be tough to distinguish whether your output code is wrong because of a bug in the compiler or because your code was just wrong. There was a change to GCC a few years back that introduced security holes into the FreeBSD and NetBSD kernel because it just threw away code that would only be invoked in "undefined behavior" scenarios. Signed integer overflow I think.
- andrewchambers 5y agoYou are unfairly comparing ancient C with modern rust - Try comparing modern C with modern rust to avoid making a straw man argument. Like I said, I don't even disagree, I still think you are just doing everyone a disservice with this line of reasoning. He said if he had used rust - I am saying if he had used C when rust was available 1. The bug would have been fixed. 2. He could have used valgrind. Modern C also has something called ubsan, and another thing called frama-C. These tools may be inferior to what rust has, but ignoring they exist or comparing 10+ year old C with modern rust is a bad faith argument.
- deleted 5y ago[deleted]
- infogulch 5y agoYes perl may have been a better choice for the projects sake, but alas the course was apparently a trial-by-~fire~segfault of C + string processing. Loved PCRE though... hmm I wonder if you could do it with just a regex...
- kragen 5y agoI will be very surprised if you can write a working spreadsheet in a PCRE regex. Perl itself permits you to embed arbitrary Perl code in a "regex", though.
- pjmlp 5y agoGCC is being written in C++ for about a decade now.