I have just looked at all the compiler warnings that were produced while building pocl with clang-3.3. More than half of these pointed to real problems, such as confusion between 64-bit and 32-bit variable types, or an accidental assignment in an if conditional. Other warnings may or may not have been errors, such as mixing up pointers to signed and unsigned types.
Since we do not use -Wall, the number of warnings one receives while building pocl is typically small, and should be zero. Many "interesting" warnings (e.g. forgetting a return statement) are not even flagged. I thus suggest to use -Werror by default, which forces people to notice warnings and act on them. Personally, I also like -Wall, but -Wall sometimes warns about things that I consider perfectly reasonable, so we may not want to use it by default. -erik -- Erik Schnetter <[email protected]> http://www.perimeterinstitute.ca/personal/eschnetter/ My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://pgp.mit.edu/.
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
