public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Richard Henderson <rth@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PR debug/46724] var-track address of RESULT_DECL
Date: Tue, 28 Dec 2010 20:26:00 -0000	[thread overview]
Message-ID: <AANLkTindYVkbc49HYU9t4cdRHCTRBCvGKcdaKP5-_s+1@mail.gmail.com> (raw)
In-Reply-To: <ork4j2zct7.fsf@livre.localdomain>

On Tue, Dec 21, 2010 at 7:49 PM, Alexandre Oliva <aoliva@redhat.com> wrote:
> On Dec 21, 2010, Richard Henderson <rth@redhat.com> wrote:
>
>> Ok, with a function comment for vt_add_function_parameter.
>
> Thanks, here's what I installed.
>

This caused:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47079

-- 
H.J.

  reply	other threads:[~2010-12-28 18:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21 10:32 Alexandre Oliva
2010-12-21 18:32 ` Richard Henderson
2010-12-22  6:37   ` Alexandre Oliva
2010-12-28 20:26     ` H.J. Lu [this message]
2010-12-29  9:17       ` Alexandre Oliva

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=AANLkTindYVkbc49HYU9t4cdRHCTRBCvGKcdaKP5-_s+1@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=aoliva@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rth@redhat.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).