memset (0, 0, 0);

[Daniel Jacobowitz]

On Fri, Apr 04, 2003 at 03:52:32PM +0100, Joern Rennecke wrote:
> On some processors, memset can be implemented more efficiently
> when you always read - and possibly also write back - the first
> memory word contained partially or in whole in the to-be-modified
> object
> 
> This conflicts with gdb usage of memset (0, 0, 0); in some places.
> There are three practical questions here:
> - should gdb use this idiom?
> - should all target-specific variants of newlib's memset implement it?
> - should all target-specific variants of glibc's memset implement it?

Where is it that GDB does this?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer