From: Pierre-Marie de Rodat <derodat@adacore.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] debug/PR78112: remove recent duplicates for DW_TAG_subprogram attributes
Date: Thu, 10 Nov 2016 11:06:00 -0000 [thread overview]
Message-ID: <5ab781cd-fc7d-5be1-5a38-cab58a6e3bff@adacore.com> (raw)
In-Reply-To: <CAFiYyc1sgPc4kcRHn0c=fpJ=dLJ3HUY+dYcF8QyQCSuJ-_uNAg@mail.gmail.com>
On 11/09/2016 10:02 AM, Richard Biener wrote:
> Using scan-assembler-times on the dwarf?
I always have a bad feeling about this kind of check as I imagine it can
break very easily with legit changes. But I have nothing better to
contribute, so I’ve added one such testcase. ;-)
>> Ok to commit?
>
> Ok.
This is committed as r242035. Thanks!
--
Pierre-Marie de Rodat
next prev parent reply other threads:[~2016-11-10 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 14:24 Pierre-Marie de Rodat
2016-11-09 9:02 ` Richard Biener
2016-11-10 11:06 ` Pierre-Marie de Rodat [this message]
2016-11-18 14:03 ` Christophe Lyon
2016-11-18 17:24 ` Pierre-Marie de Rodat
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=5ab781cd-fc7d-5be1-5a38-cab58a6e3bff@adacore.com \
--to=derodat@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--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).