|
You are here |
gustedt.wordpress.com | ||
| | | | |
cellperformance.beyond3d.com
|
|
| | | | | [AI summary] The provided text discusses strict aliasing in C programming, particularly in the context of the C99 standard. It explains how strict aliasing rules prevent different types from referring to the same memory location, and how this affects compiler optimizations. The text also covers the use of standard integer types like uint64_t and uint32_t from the C99 stdint.h header, and emphasizes the importance of enabling strict aliasing with GCC's -fstrict-aliasing flag for performance and correctness. | |
| | | | |
www.ralfj.de
|
|
| | | | | In my previous blog post on pointer provenance, I have shown that not thinking carefully about pointers can lead to a compiler that is internally inconsistent: programs that are intended to... | |
| | | | |
stefansf.de
|
|
| | | | | In this article we examine the strict aliasing rules of the C programming language which are the basis for Type-Based Alias Analysis and show some quirks | |
| | | | |
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... | ||