On Wed, Jan 30, 2013 at 6:22 PM, Nico Weber <tha...@chromium.org> wrote:
> On Wed, Jan 30, 2013 at 7:29 AM, Vane, Edwin <edwin.v...@intel.com> wrote:
>> Dmitri wrote:
>>> If this is the only false positive, I think it is worth working around the
>>> warning.
>>
>> This is indeed the only instance of this empty {} warning bug in the gcc
>> build.
>
> There will likely be more in the future.
>
> The clang bots should catch the problems detected by this warning
> reliably without false positives, right?
Not now. This warning is off by default in Clang:
def warn_missing_field_initializers : Warning<
"missing field '%0' initializer">,
InGroup<MissingFieldInitializers>, DefaultIgnore;
Dmitri
--
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <griboz...@gmail.com>*/
_______________________________________________
cfe-commits mailing list
cfe-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
