From: Andrew Haley <aph@redhat.com>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: gcc-patches@gcc.gnu.org, gerald@pfeifer.com, hp@bitrange.com,
james.greenhalgh@arm.com, joseph@codesourcery.com,
limegreensocks@yahoo.com, rdsandiford@googlemail.com
Subject: Re: [DOC PATCH] Rewrite docs for inline asm
Date: Mon, 28 Apr 2014 08:57:00 -0000 [thread overview]
Message-ID: <535E0F58.3020907@redhat.com> (raw)
In-Reply-To: <20140427105617.C8E4233CA0@vlsi1.gnat.com>
On 04/27/2014 11:56 AM, Richard Kenner wrote:
>>>>> any symbols it references. This may result in those symbols getting
>>>>> discarded by GCC as unreferenced.
>>>
>>> We can omit "by GCC" here.
>>
>> We can, but we should not. We should avoid the passive voice like the
>> plague in technical documentation, even if doing so leads to some
>> slight redundancy.
>
> I agree, but that's still passive voice (you need not omit the actor to be
> using passive voice)! Active voice (which is indeed preferred) is "This
> may result in GCC discarding those symbols as unreferenced."
Indeed. That's definitely better.
Andrew.
next prev parent reply other threads:[~2014-04-28 8:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 19:48 dw
2014-04-08 23:17 ` Hans-Peter Nilsson
2014-04-09 5:02 ` Michael Matz
2014-04-09 5:29 ` dw
2014-04-10 21:44 ` dw
2014-04-13 1:47 ` Hans-Peter Nilsson
2014-04-13 9:42 ` dw
2014-04-14 0:46 ` Hans-Peter Nilsson
2014-04-14 6:25 ` dw
2014-04-23 3:44 ` Chung-Ju Wu
2014-04-23 5:52 ` Chung-Ju Wu
2014-04-25 15:45 ` James Greenhalgh
2014-04-25 15:59 ` Andrew Haley
2014-04-27 0:21 ` Gerald Pfeifer
2014-04-27 9:32 ` Andrew Haley
2014-04-27 11:57 ` Richard Kenner
2014-04-28 8:57 ` Andrew Haley [this message]
2014-04-27 23:07 ` dw
2014-04-29 11:07 ` dw
2014-04-29 12:55 ` Richard Earnshaw
2014-04-30 2:38 ` dw
2014-05-05 20:23 ` Gerald Pfeifer
2014-05-06 5:12 ` dw
2014-05-07 5:47 ` dw
2014-05-06 7:58 ` Andrew Haley
2014-05-29 10:24 ` Eric Botcazou
2014-05-29 11:51 ` Andrew Haley
2014-05-29 21:18 ` Eric Botcazou
2014-05-07 16:55 ` Joseph S. Myers
2016-06-17 14:54 ` Andrew Haley
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=535E0F58.3020907@redhat.com \
--to=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=hp@bitrange.com \
--cc=james.greenhalgh@arm.com \
--cc=joseph@codesourcery.com \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=limegreensocks@yahoo.com \
--cc=rdsandiford@googlemail.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).