Timeline for code generation - would C be a good compiler backend?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 6, 2020 at 4:25 | review | Close votes | |||
| Feb 12, 2020 at 3:05 | |||||
| Feb 6, 2020 at 0:25 | vote | accept | Kied Llaentenn | ||
| Feb 6, 2020 at 0:14 | answer | added | Christophe | timeline score: 10 | |
| Feb 6, 2020 at 0:00 | history | tweeted | twitter.com/StackSoftEng/status/1225207642102157312 | ||
| Feb 5, 2020 at 23:21 | answer | added | Telastyn | timeline score: 8 | |
| Feb 5, 2020 at 23:05 | comment | added | Robert Harvey | In this space, you're going to find two kinds of people, the ones that have an opinion because they think they know, and the ones that actually know because they've tried it (I'm in the former category). According to the post you linked, the ones who object to C as a backed have tried and failed, and ultimately settled on emitting processor instructions or byte code. The LLVM project apparently went through this life-cycle, as they used to have a C backend that isn't supported or maintained anymore. | |
| Feb 5, 2020 at 23:04 | comment | added | Robert Harvey | Good compilers rely on being fed reasonably canonical code, and the C code generated by a transpiler is unlikely to look like that. Hence the objections about performance (probably). | |
| Feb 5, 2020 at 23:03 | answer | added | Deduplicator | timeline score: 2 | |
| Feb 5, 2020 at 22:25 | review | First posts | |||
| Feb 6, 2020 at 22:16 | |||||
| Feb 5, 2020 at 22:21 | history | asked | Kied Llaentenn | CC BY-SA 4.0 |