From: Diego Novillo <dnovillo@google.com>
To: Eric Fisher <joefoxreal@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: a mistake in gccint doc
Date: Fri, 15 May 2009 23:16:00 -0000 [thread overview]
Message-ID: <b798aad50905151445l6fd7fdf5kb46eefc2cd0a979d@mail.gmail.com> (raw)
In-Reply-To: <d6afecde0905142312h149a7facx4bee2474d5636be2@mail.gmail.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.
next prev parent reply other threads:[~2009-05-15 21:45 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 [this message]
2009-05-16 9:29 ` Eric Fisher
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=b798aad50905151445l6fd7fdf5kb46eefc2cd0a979d@mail.gmail.com \
--to=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=joefoxreal@gmail.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).