From: Cary Coutant <ccoutant@google.com>
To: Sterling Augustine <saugustine@google.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, reply@codereview.appspotmail.com
Subject: Re: [google 4.7] Fix for PR 8013197 (issue7140044)
Date: Fri, 18 Jan 2013 19:05:00 -0000 [thread overview]
Message-ID: <CAHACq4qdP2kS2pYfRvmDTCDUHNpeX4jfow1g8WciZBjW66mfFg@mail.gmail.com> (raw)
In-Reply-To: <CAHACq4p3-ysM+VhAHuzt+zOcL5be711gNGsrzwYO_+k2ivN+iQ@mail.gmail.com>
>> 2013-01-16 Sterling Augustine <saugustine@google.com>
>>
>> * gcc/dwarf2out.c (resolve_addr): Delete call to
>> remove_addr_table_entry.
>
> OK for google/gcc-4_7. The commit log entry should say "Google ref:
> b/8013197" instead of "PR ...".
I'll file an upstream bug for this as well (as soon as I can get the
test case reduced enough), and I'd like to get this fix into 4.8.
-cary
prev parent reply other threads:[~2013-01-18 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 21:37 Sterling Augustine
2013-01-17 0:21 ` Cary Coutant
2013-01-17 22:01 ` Sterling Augustine
2013-01-18 19:05 ` Cary Coutant [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=CAHACq4qdP2kS2pYfRvmDTCDUHNpeX4jfow1g8WciZBjW66mfFg@mail.gmail.com \
--to=ccoutant@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=reply@codereview.appspotmail.com \
--cc=saugustine@google.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).