Tried to fix the warning, and I'm not now sure if the warning makes sense. These "'~': zero extending '<smaller integer type>' to 'int64_t' of greater size" warning may be annoying as it is issued for code like "int64_t x ~<some-int32_t-var>". Probably we should disable the warning instead? On Tue, Feb 9, 2016 at 11:15 AM, Rafael Espíndola < rafael.espindola at gmail.com> wrote:> Sounds good to me :-) > > Cheers, > Rafael > > > On 9 February 2016 at 13:59, Rui Ueyama <ruiu at google.com> wrote: > > Reid said that he has disabled non-x86-64 backends for the clang/win64 > > buildbot, so maybe this is the first time for us to see these warnings. > But > > all of them seem to be easily fixable, so why don't we do that. > > > > On Tue, Feb 9, 2016 at 10:49 AM, Rafael Espíndola > > <llvm-commits at lists.llvm.org> wrote: > >> > >> Most of the warnings are actually in LLVM code. Any reason we don't > >> see it in other bots? > >> > >> Cheers, > >> Rafael > >> > >> > >> On 9 February 2016 at 13:02, Galina Kistanova via llvm-commits > >> <llvm-commits at lists.llvm.org> wrote: > >> > Hello everyone, > >> > > >> > The builder http://lab.llvm.org:8011/builders/lld-x86_64-win7 is up > and > >> > running. It builds lld and runs lld tests for each commit. > >> > The build shows 11 warnings, everything else is green. > >> > > >> > Do you think it is feasible to treat warnings as errors, or better > keep > >> > it > >> > this way for now? > >> > > >> > Thanks > >> > > >> > Galina > >> > > >> > _______________________________________________ > >> > llvm-commits mailing list > >> > llvm-commits at lists.llvm.org > >> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits > >> > > >> _______________________________________________ > >> llvm-commits mailing list > >> llvm-commits at lists.llvm.org > >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits > > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160209/08a88a3c/attachment.html>
Joerg Sonnenberger via llvm-dev
2016-Feb-09 23:03 UTC
[llvm-dev] Builder lld-x86_64-win7 is back
On Tue, Feb 09, 2016 at 02:40:06PM -0800, Rui Ueyama via llvm-commits wrote:> Tried to fix the warning, and I'm not now sure if the warning makes sense. > These "'~': zero extending '<smaller integer type>' to 'int64_t' of greater > size" warning may be annoying as it is issued for code like "int64_t x > ~<some-int32_t-var>".This sounds like something were the semantic of the code is not obviously what was originally intended. Joerg
On Tue, Feb 9, 2016 at 3:03 PM, Joerg Sonnenberger via llvm-commits < llvm-commits at lists.llvm.org> wrote:> On Tue, Feb 09, 2016 at 02:40:06PM -0800, Rui Ueyama via llvm-commits > wrote: > > Tried to fix the warning, and I'm not now sure if the warning makes > sense. > > These "'~': zero extending '<smaller integer type>' to 'int64_t' of > greater > > size" warning may be annoying as it is issued for code like "int64_t x > > ~<some-int32_t-var>". > > This sounds like something were the semantic of the code is not > obviously what was originally intended. >So you thought that was useful? Then why doesn't clang/gcc warn on that?> > Joerg > _______________________________________________ > llvm-commits mailing list > llvm-commits at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160209/f99df456/attachment.html>