From: Gerald Pfeifer <gerald@pfeifer.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [Patch,wwwdocs,AVR]: AVR release notes
Date: Sun, 29 Jan 2012 23:27:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1201300020280.2227@gerinyyl.fvgr> (raw)
In-Reply-To: <4F19B2BB.2020401@gjlay.de>
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
next prev parent reply other threads:[~2012-01-29 23:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 18:30 Georg-Johann Lay
2012-01-25 15:57 ` Ping #1: " Georg-Johann Lay
2012-01-29 23:27 ` Gerald Pfeifer [this message]
2012-01-30 13:55 ` Georg-Johann Lay
2012-01-30 18:59 ` Weddington, Eric
2012-01-30 23:07 ` Georg-Johann Lay
2012-02-12 22:23 ` Gerald Pfeifer
2012-02-13 14:28 ` Weddington, Eric
2012-02-15 17:04 ` Georg-Johann Lay
2012-02-15 17:17 ` Georg-Johann Lay
2015-04-11 0:02 ` Gerald Pfeifer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.00.1201300020280.2227@gerinyyl.fvgr \
--to=gerald@pfeifer.com \
--cc=avr@gjlay.de \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).