When compiling with gcc for Windows, there are a bunch of warnings that fall into (at least) four categorizes: a) unknown pragmas that are caused by MSVC's pragma warning features (which I intend to disable project wide in this build config) b) Unused variables c) Unused functions d) signed/unsigned comparisons Several instances of (d) is caused by constant mismatching: TLS_OUT_OF_INDEXES is a DWORD according to microsoft, which is an unsigned int. We treat it as a long. The attached patch resolves a through c. I'd like guidance on what to do for (d), maybe some combination of: try to fix them in mozilla codebase, file a bug upstream, ignore them. Ignoring them will require disabling warnings-as-errors for this project in the mingw build. (Which I am okay with.)

Flagging a couple peers in IPC to get input on what they would like to see.

We can suppress the warnings, but the error log might be interesting — patches to clean up ipc/chromium/src, especially if they're mostly or entirely deletions, are of interest. (For better or worse, it's a hard fork of upstream Chromium and won't be merged except maybe by throwing it all out and starting over, so we're free to alter it.)

What Jed said. Eventually I'd like to throw the chromium bits all out.