Kamil Dudka wrote:
It can cause a real crash in certain execution environments.
Which ones? I'm not interested in environments like -fsanitize=undefined, which is designed to catch violations of the standard. I want to know of a real execution environment where memcpy (0, 0, 0) does something bad, and why it does so.
