public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Jason Merrill <jason@redhat.com>,
	Richard Biener <richard.guenther@gmail.com>,
	gcc-patches List <gcc-patches@gcc.gnu.org>,
	ccoutant@gmail.com
Subject: Re: [PR59319] output friends in debug info
Date: Mon, 10 Apr 2017 16:24:00 -0000	[thread overview]
Message-ID: <039A42A0-4B23-4A47-A635-910D5D5BA02F@comcast.net> (raw)
In-Reply-To: <ormvbs2hnj.fsf@lxoliva.fsfla.org>

On Apr 7, 2017, at 11:32 AM, Alexandre Oliva <aoliva@redhat.com> wrote:
> 
> On Mar 21, 2017, Alexandre Oliva <aoliva@redhat.com> wrote:
>> 
>> Ping?  https://gcc.gnu.org/ml/gcc-patches/2017-01/msg02112.html
> Ping?

The Objective-C/C++ parts look fine.

  reply	other threads:[~2017-04-10 16:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 18:47 Alexandre Oliva
2016-08-22 11:36 ` Richard Biener
2016-08-26  5:26   ` Alexandre Oliva
2016-08-26  8:59     ` Richard Biener
2016-08-26 16:13 ` Jason Merrill
2016-08-30 23:13   ` Alexandre Oliva
2016-09-24  2:39     ` Alexandre Oliva
2016-10-19 10:17       ` Alexandre Oliva
2017-01-27  6:27         ` Alexandre Oliva
2017-03-21 18:35           ` Alexandre Oliva
2017-04-07 18:32             ` Alexandre Oliva
2017-04-10 16:24               ` Mike Stump [this message]
2017-12-07 21:04               ` Alexandre Oliva
2017-12-14 18:48                 ` Jason Merrill
2017-12-19 21:57                   ` Alexandre Oliva
2017-12-21 22:37                     ` Jason Merrill
2017-04-12 22:06             ` Jeff Law

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=039A42A0-4B23-4A47-A635-910D5D5BA02F@comcast.net \
    --to=mikestump@comcast.net \
    --cc=aoliva@redhat.com \
    --cc=ccoutant@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=richard.guenther@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).