From: Eric Fisher <joefoxreal@gmail.com>
To: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org,
Diego Novillo <dnovillo@google.com>
Subject: Re: a mistake in gccint doc
Date: Sat, 16 May 2009 09:29:00 -0000 [thread overview]
Message-ID: <d6afecde0905152043u16d2d7fdw4b5f58ddcbe140c8@mail.gmail.com> (raw)
In-Reply-To: <b798aad50905151445l6fd7fdf5kb46eefc2cd0a979d@mail.gmail.com>
2009/5/16 Diego Novillo <dnovillo@google.com>:
> On Fri, May 15, 2009 at 02:12, Eric Fisher <joefoxreal@gmail.com> wrote:
>
>> I think it's a mistake between a and b. It should be,
>>
>> "
>> variable @code{a} is completely modified with the contents of
>> variable @code{b}. Real definition are also known as @dfn{killing
>> definitions}. Similarly, the use of @code{b} reads all its bits.
>> "
>
> Thanks, could you send a patch for tree-ssa.texi?
>
>
> Diego.
>
This is a patch for tree-ssa.texi, which corrects the mistake between a and b.
2009-05-16 Eric Fisher <joefoxreal@gmail.com>
* gcc/doc/tree-ssa.texi: fix a mistake in SSA Operands section
Index: tree-ssa.texi
===================================================================
--- tree-ssa.texi (revision 147604)
+++ tree-ssa.texi (working copy)
@@ -108,9 +108,9 @@ full object that they represent. For in
Since @code{a} and @code{b} are non-aliased locals, the statement
@code{a = b} will have one real definition and one real use because
-variable @code{b} is completely modified with the contents of
-variable @code{a}. Real definition are also known as @dfn{killing
-definitions}. Similarly, the use of @code{a} reads all its bits.
+variable @code{a} is completely modified with the contents of
+variable @code{b}. Real definition are also known as @dfn{killing
+definitions}. Similarly, the use of @code{b} reads all its bits.
In contrast, virtual operands are used with variables that can have
a partial or ambiguous reference. This includes structures, arrays,
prev parent reply other threads:[~2009-05-16 3:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 16:34 Eric Fisher
2009-05-15 23:16 ` Diego Novillo
2009-05-16 9:29 ` Eric Fisher [this message]
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=d6afecde0905152043u16d2d7fdw4b5f58ddcbe140c8@mail.gmail.com \
--to=joefoxreal@gmail.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@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).