From: "Weddington, Eric" <Eric.Weddington@atmel.com>
To: "Georg-Johann Lay" <avr@gjlay.de>, <gcc-patches@gcc.gnu.org>
Cc: "Gerald Pfeifer" <gerald@pfeifer.com>,
"Denis Chertykov" <chertykov@gmail.com>
Subject: RE: [Patch,wwwdocs,AVR]: AVR release notes
Date: Mon, 30 Jan 2012 18:59:00 -0000 [thread overview]
Message-ID: <8D64F155F1C88743BFDC71288E8E2DA806D3EC05@csomb01.corp.atmel.com> (raw)
In-Reply-To: <4F26A14D.4050207@gjlay.de>
> -----Original Message-----
> From: Georg-Johann Lay
> Sent: Monday, January 30, 2012 6:55 AM
> To: gcc-patches@gcc.gnu.org
> Cc: Gerald Pfeifer; Denis Chertykov; Weddington, Eric
> Subject: Re: [Patch,wwwdocs,AVR]: AVR release notes
>
> Attached an updated patch as there were many changes and so that Eric
and
> Denis
> can easier catch up.
Hi Johann,
Comments:
In the first hunk of the patch, you say that libgcc has been improved
and enhanced. Can you elaborate just a little in the docs as to how it
has been improved and enhanced? The reason is that we are telling users
that they have recompile all their code with a new version of gcc
because of these improvements and enhancements, but I think we are too
vague in giving them a reason. Users will want to know why they have to
do a rebuild. It doesn't have to go into great detail, but just a little
less vague.
s/Support has beed added/Support has been added/
If the list of built-in functions added is really long, I'm ok leaving
out the whole list. But, can we give some sort of short description as
to the types of built-in functions added?
Other than those things, the updated patch looks good to me. Let me know
if I can help with wording / language.
Eric Weddington
next prev parent reply other threads:[~2012-01-30 18:59 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
2012-01-30 13:55 ` Georg-Johann Lay
2012-01-30 18:59 ` Weddington, Eric [this message]
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=8D64F155F1C88743BFDC71288E8E2DA806D3EC05@csomb01.corp.atmel.com \
--to=eric.weddington@atmel.com \
--cc=avr@gjlay.de \
--cc=chertykov@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/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).