[lldb-dev] (no subject)
spucci at google.com
Sat Mar 15 09:42:44 PDT 2014
On Linux/gcc, the great majority of warnings is for a warning about using
%p in a printf with a void* argument, which IMHO is a bogus warning that
only gcc emits, and AFAICT can't be disabled without disabling the other
far-more-useful printf warnings. I wound up writing a script to filter
these out from my build logs rather than try to fix them all.
On Sat, Mar 15, 2014 at 9:30 AM, Saleem Abdulrasool
<compnerd at compnerd.org>wrote:
> As the LLDB build currently exists, there are a large number of warnings
> which clutter the build. This is even worse on Linux when building with
> I was wondering if there would be any objection to forcing errors on
> warnings as they as they get cleaned up. This requires that the compiler
> support marking certain warnings a errors (i.e. -Werror=*). clang and gcc
> support many of these, and this would need to be conditionalised on
> compiler support to ensure that no one is prevented from continuing to
> build LLDB.
> LLVM actually has buildbots that build with -Werror which helps prevent
> new errors from being integrated in clang and LLVM, unfortunately, the
> buildbot situation for LLDB is not as pretty. As such, I was wondering if
> it would be acceptable to push this down into the normal build.
> Saleem Abdulrasool
> compnerd (at) compnerd (dot) org
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev