Date: Thu, 17 Nov 2005 14:51:39 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Stefan Farfeleder <stefanf@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, Ariff Abdullah <ariff@FreeBSD.org> Subject: Re: cvs commit: src/sys/dev/sound/pcm channel.c Message-ID: <20051117145139.h0rxsukk74wog4c8@netchild.homeip.net> In-Reply-To: <20051115124331.GD9996@wombat.fafoe.narf.at> References: <200511150419.jAF4JRUp080869@repoman.freebsd.org> <20051115105128.a5dd001i0ckock0s@netchild.homeip.net> <20051115095801.M61850@fledge.watson.org> <20051115202306.4cf2dcf2.ariff@FreeBSD.org> <20051115124331.GD9996@wombat.fafoe.narf.at>
next in thread | previous in thread | raw e-mail | index | archive | help
Stefan Farfeleder <stefanf@FreeBSD.org> wrote: > On Tue, Nov 15, 2005 at 08:23:06PM +0800, Ariff Abdullah wrote: >> On Tue, 15 Nov 2005 09:58:52 +0000 (GMT) >> Robert Watson <rwatson@FreeBSD.org> wrote: >> > Probably a combination of -Wall and -Werror, which generally >> > generates a warning along the following lines: >> > >> > warning: suggest parentheses around comparison in operand of & >> > >> That means, warnings caused by excessive inlining while compiling >> maestro.c should also break the build if WARNS=1, right? Has anybody >> encounter and getting annoyed by this? > > No, function inlining doesn't change the semantics of expressions. So -Wall and -Werror doesn' result in issuing an error for each warning but instead in an error for warnings, which are issued because the code in question may change the semantic depending on the change which needs to be done to get rid of the warning? Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 BOFH excuse #173: Recursive traversal of loopback mount points
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051117145139.h0rxsukk74wog4c8>