Bruno Haible <[EMAIL PROTECTED]> writes: > Changing the function definition to use ANSI C argument list syntax (without > adding 'restrict' there) fixes the problem. Changing the function definition > by adding 'restrict' in the first and fourth argument (keeping the K&R syntax) > also fixes the problem. > > Which fix to choose? Which one is likely to please the glibc developers > better?
Let's keep the K&R syntax please. Other glibc developers prefer that for some obscure reason (for external functions only). Thanks for finding this problem.
