On Wed, 24 Aug 2016, David Malcolm wrote: > This covers my changes so far for gcc 7
That's lot! :-) > (I don't have a working copy of mhc, so I can't easily test the CSS > markup) Do not worry about that. The idea really is to treat the pages as standard HTML and minimize use of mhc for things like footers which should not impact editing much. Index: htdocs/gcc-7/changes.html =================================================================== + <li>gcc 6's C and C++ frontends were able to offer suggestions for "GCC" (all upper-case) + gcc 7 greatly expands the scope of these suggestions. Firstly, it "GCC" + <li>gcc's preprocessor can now offer suggestions for misspelled How about just saying "The preprocessor..." here? (As you prefer, though.) +<p>libgccjit performs numerous checks at the API boundary, but +if these succeed, it previously ignored errors and other diagnostics emitted +within the core of gcc, and treated the compile of a gcc_jit_context +as having succeeded. As of gcc 7 it now ensures that if any diagnostics are +emitted, they are visible from the libgccjit API, and that the the context is +flagged as having failed.</p> "GCC" (twice) + <li>The <code>gcc</code> and <code>g++</code> driver programs will now + provide suggestions for misspelled arguments to command line options. "command-line options" (per codingconventions.html) + <li>GCC has gained an internal unit-testing framework, allowing for + more detailed testing of its implementation details.</li> On this I would argue you actually did more than that: not only does GCC now have such a framework, there is a growing number of tests leveraging that, too. Don't be too modest. ;-) Oh, and of course this change is fine, modulo my feedback. Thanks, Gerald
