------- Comment #10 from joseph at codesourcery dot com 2010-05-12 11:52 ------- Subject: Re: Incorrect nonnull assumed in code generation
On Wed, 12 May 2010, pmoulder at mail dot csse dot monash dot edu dot au wrote: > Coming back to memcpy etc.: As this is such an edge case, I'll give more > detail > for my (revised) reasoning (partly for the benefit of certain others that I > intend to refer to this discussion): It's a case about which the standard is completely explicit. 7.21.1#2. "Where an argument declared as size_t n specifies the length of the array for a function, n can have the value zero on a call to that function. Unless explicitly stated otherwise in the description of a particular function in this subclause, pointer arguments on such a call shall still have valid values, as described in 7.1.4." -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44081
