Date: Mon, 09 Feb 2009 15:08:30 +0100 From: Christoph Mallon <christoph.mallon@gmx.de> To: Hans Petter Selasky <hselasky@c2i.net> Cc: usb@freebsd.org, freebsd-current@freebsd.org, Alfred Perlstein <alfred@freebsd.org> Subject: Re: HEADSUP usb2/usb4bsd to become default in GENERIC Message-ID: <499038DE.3050501@gmx.de> In-Reply-To: <200902091450.07014.hselasky@c2i.net> References: <20090206045349.GQ78804@elvis.mu.org> <49901276.5040604@gmx.de> <49901399.8070409@gmx.de> <200902091450.07014.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hans Petter Selasky schrieb: > On Monday 09 February 2009, Christoph Mallon wrote: >> Christoph Mallon schrieb: >>> are named "err" or "error". This should be investigated, so here's the >>> complete list: >> Sorry, my MUA seems to have damaged the list. You can get the list here: >> http://tron.homeunix.org/usb2.unread.log > > I think some of these errors depend if you have USB debugging compiled or not. > At least GCC does not warn? No, it does not depend on USB debugging. GCC has no warning at all for variables which are only assigned to. It only can warn about variables, which are only initialised. { int x = 23; // GCC warns here ... int y; // ... but not here - cparser does y = 42; y++; } cparser has an analysis, which can warn about "y", too. I manually verified all 40 warnings and I cannot find any users (i.e. readers) for these variables.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?499038DE.3050501>