[cfe-dev] boost warnings when using clang

[James Gregurich]

test was codeD TO input *

On Aug 14, 2012, at 3:19 PM, James Gregurich <bayoubengal at me.com> wrote:

> 
> in the specific instance I looked at (in the date time library), the conversion would not fail unless the test was code input something like 4294967296 hours. 
> 
> 
> On Aug 14, 2012, at 2:31 PM, Eli Friedman <eli.friedman at gmail.com> wrote:
> 
>> On Tue, Aug 14, 2012 at 2:20 PM, James Gregurich <bayoubengal at me.com> wrote:
>>> When I compile apps that use boost classes (boost 1.49), I get a number of compiler warnings.  I looked at one of them and it looks like a legitimate warning as they are doing an operation that results in a long being being converted to an int on 64 bit. I'm a bit puzzled how such a problem would not get fixed during the development cycle. Perhaps clang catches more issues than gcc or perhaps their macro usage causes the correct behavior on gcc but not on clang.
>>> 
>>> Does anyone on the clang team communicate with the  boost people to let them know when clang reports a warning that might be going unseen with gcc or VC++? If not, perhaps I should report them as their presence in my build logs bugs me.
>> 
>> If you see issues which seem like bugs in boost, please report them
>> (it looks like http://www.boost.org/support/bugs.html has their bug
>> reporting guidelines).  We have a buildbot running the boost
>> regression tests, but we wouldn't notice any compiler warnings coming
>> out of it as long as the tests pass.
>> 
>> -Eli
>> 
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>