Fix some clang warnings with -Wmissing-braces in base.

base/third_party/nspr/prtime.cc

Index: base/third_party/nspr/prtime.cc
diff --git a/base/third_party/nspr/prtime.cc b/base/third_party/nspr/prtime.cc
index 9335b01de863ca5fdef0e0c3122396a5fd5ed3bb..a7c5a3a949680ae87541d86e8c032a9fb432eab5 100644
--- a/base/third_party/nspr/prtime.cc
+++ b/base/third_party/nspr/prtime.cc
@@ -107,9 +107,9 @@ PR_ImplodeTime(const PRExplodedTime *exploded)
     static const PRTime kSecondsToMicroseconds = static_cast<PRTime>(1000000);
 #if defined(OS_WIN)
    // Create the system struct representing our exploded time.
-    SYSTEMTIME st = {0};
-    FILETIME ft = {0};
-    ULARGE_INTEGER uli = {0};
+    SYSTEMTIME st = {};

[Nico, 2015/07/01 18:40:49]

This is a third-party file. Update base/third_party/README.chromium and upstream
this to nspr

[dcheng, 2015/07/01 21:26:38]

It doesn't appear anyone has ever updated README.chromium other than to make
check-licenses and some other licensing stuff happy:
https://chromium.googlesource.com/chromium/src/+log/master/base/third_party/n...

In addition, upstream appears to have diverged significantly:
https://hg.mozilla.org/projects/nspr/file/cf176edf81f2/pr/src/misc/prtime.c#l229

Given that this is essentially a forked copy of prtime.c at this point, is it OK
to just keep this part as is?

+    FILETIME ft = {};
+    ULARGE_INTEGER uli = {};
 
     st.wYear = exploded->tm_year;
     st.wMonth = static_cast<WORD>(exploded->tm_month + 1);