It's not a bug. It actually comes from the warning -Wmemset-transposed-args
which is active with -Wall and I had a short look that it seems to be that
there were several bugs with false positives for this warning and as far as
I can understand the gcc developers did not
rule out to issue the warning even if memset(*,0,0) is used.


2015-08-20 17:08 GMT+02:00 Richard Hipp <drh at sqlite.org>:

> On 8/20/15, Bernhard Schommer <bernhardschommer at gmail.com> wrote:
> > Hi,
> >
> > the problem is that this is a warning generated by the linker to warn the
> > user that
> > he potential swapped the arguments which it does since 0 occurs more
> often
> > on
> > the value side and memset(*,0,0) actually does nothing.
> >
>
> My contention remains that this is a bug in the compiler/linker.

--
> D. Richard Hipp
> drh at sqlite.org
> _______________________________________________
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

Reply via email to