Date: Sun, 17 May 2009 20:04:56 +0400 From: Stanislav Sedov <stas@FreeBSD.org> To: Christoph Mallon <christoph.mallon@gmx.de> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: C99: Suggestions for style(9) Message-ID: <20090517200456.cefa04fb.stas@FreeBSD.org> In-Reply-To: <4A1004B3.5040805@gmx.de> References: <49F4070C.2000108@gmx.de> <20090428114754.GB89235@server.vk2pj.dyndns.org> <49FAE4EA.1010205@gmx.de> <20090517144516.331b01a8.stas@FreeBSD.org> <4A1004B3.5040805@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 17 May 2009 14:36:03 +0200 Christoph Mallon <christoph.mallon@gmx.de> mentioned: > > > Aliasing behavior is stritcly described in > > ISO C99 standard, so there's a good point to enforcing strict-aliasing clear > > code in our kernel. > If you like this addition because of this reason, I have to disappoint > you: This addition has absolutly *nothing* to do with strict-aliasing. > I didn't meant I like this change only from aliasing point of view: certianly, the code readability argument is very important. But this change also works towards the strict aliasing problem solving too: there's just a less chance someone will reuse a variable, address of which was previously taken. > > On the other hand the big work should be done on clearing > > the existing code before any rule on this can be enforced. > This addition is about improving readability for humans, because it > simplifies the def-use-chains, and as a side effect sometimes leads to > better generated code. It is not sensible to check millions of lines of > code whether a variables are used in different contexts within a > function before this can added. > -- Stanislav Sedov ST4096-RIPE !DSPAM:4a103589994292021119546!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090517200456.cefa04fb.stas>