Explore >> Select a destination
|
You are here 
|
blog.sigplan.org | ||
| | | | |
davmac.wordpress.com
|
|
| | | | | A discussion of undefined behaviour and compiler optimisation, particularly in regards to signed integer overflow. C (and C++) compilers are becoming notorious for exploiting the notion of undefined behaviour - the idea that certain things a program might do have no behaviour proscribed by the language standard, and that the compiler can assume the program... | |
| | | | |
blog.regehr.org
|
|
| | | | | [AI summary] The provided text is a discussion thread about undefined behavior in C and C++ programming languages, focusing on integer overflow, pointer aliasing, and compiler optimizations. Key points include the implications of undefined behavior in real-world code, the role of compilers in handling such cases, and the balance between adhering to standards and accommodating practical programming needs. The conversation touches on tools for detecting undefined behavior, the evolution of C/C++ standards, and the importance of unit testing and maintenance in software development. | |
| | | | |
qsantos.fr
|
|
| | | | | [AI summary] This article explains the dangers of undefined behavior in programming languages like C, illustrates how compiler optimizations can lead to unpredictable results, and reviews various static and formal analysis tools used to detect and prevent such issues. | |
| | | | |
craftinginterpreters.com
|
|
| | | [AI summary] The text discusses the implementation of a compiler for a simple programming language, focusing on parsing and bytecode generation. It covers topics such as recursive descent parsing, Pratt parsing, and the use of a parser table to handle operator precedence. The text also includes code snippets for the parser and compiler functions, as well as instructions for debugging and testing the compiler. The author emphasizes the importance of error handling and the use of a debug flag to enable the printing of generated bytecode. | ||
