strange issue reading /dev/null

[Peter Jeremy]

On 2008-Aug-07 12:19:20 -0500, "Sean C. Farley" <scf at freebsd.org> wrote:
>Grr!  Optimization should not be a requirement for checking for
>uninitialized variables.  Yes, gcc adds "fun" to development.

This is documented:
`-Wuninitialized'
     Warn if an automatic variable is used without first being
     initialized or if a variable may be clobbered by a `setjmp' call.

     These warnings are possible only in optimizing compilation,
     because they require data flow information that is computed only
     when optimizing.  If you do not specify `-O', you will not get
     these warnings. Instead, GCC will issue a warning about
     `-Wuninitialized' requiring `-O'.

That explanation makes sense.

-- 
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080807/aab2e92f/attachment.pgp