On Fri, 20 Jan 2012, Georg-Johann Lay wrote: > Adding AVR-specific release notes to wwwdocs/htdocs/gcc-4.7/changes.html
Index: changes.html =================================================================== + <li>The AVR port's libgcc has been improved and its multilib structure + has been enhanced. As a result, all objects contributing to an + application must either be compiled with GCC versions up to 4.6.x or + with GCC versions ≥ 4.7.</li> How about "...compiled with older versions of GCC, up to GCC 4.6.x, or GCC 4.7.0 and later" ? And I'd omit the just ≥4.7.0 should work? + <li>Support has beed added for instrinsic named address spaces "Support for...has been added" (also typo: beed -> been) + <code>__pgm</code>, <code>__pgm1</code>, …, <code>__pgm5</code> How about omitting here? + and <code>__pgmx</code>. These address spaces locate read-only data in + flash memory and allow reading from flash memory by means of vanilla + C instructions, i.e. without the need of (inline) assembler code.</li> What's a C instruction? C builtins? + <li>Support for AVR-specific built-in functions has beed added.</li> Which ones? + <li>New command-line options <code>-maccumulate-args</code>, + <code>-mbranch-cost=<i>cost</i></code> and <code>-mstrict-X</code> + were added to allow better fine-tuning of code optimization.</li> Should X be put under <i>...</i> here, to? + <li>Many optimizations to: + <ul> + <li>64-bit integer arithmetic</li> + <li>Widening multiplication</li> + <li>Integer divide-by-constant</li> "division by a constant" + <li>Generic built-in functions + like <code>__builtin_ffs*</code>, <code>__builtin_clz*</code>, etc.</li> I don't think we need here. Breaing the lines here is something a web browser should avoid, but it is not verboten, technically. + <li>Merging of data in <code>.progmem</code></li> What is ".progmen"? Perhaps paraphrase this briefly? The update is fine assuming you look into my suggestions. Thanks you, Gerald
