On Sun, 17 May 2009 14:36:03 +0200 Christoph Mallon <christoph.mal...@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! _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
