From: "Ian Lance Taylor via gcc-patches" <gcc-patches@gcc.gnu.org>
To: Denis Khalikov <d.khalikov@partner.samsung.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][PR sanitizer/77631] Support separate debug info in libbacktrace
Date: Tue, 14 Mar 2017 13:21:00 -0000 [thread overview]
Message-ID: <CAKOQZ8xenKq1_1W8d6ZnirySXxPSTwnFt2p0WrvuO4WdMdCPQQ@mail.gmail.com> (raw)
In-Reply-To: <4619f6ae-bce8-89d3-6ba9-5d4fb95eb52d@partner.samsung.com>
On Tue, Mar 14, 2017 at 3:20 AM, Denis Khalikov
<d.khalikov@partner.samsung.com> wrote:
> Thanks for review,
>
>> Skimming over the patch I noticed you duplicate libiberties xcrc32
>> functionality.
>
> should i take care about standalone libbacktrace ?
> https://github.com/ianlancetaylor/libbacktrace
No, don't worry about it.
Ian
next prev parent reply other threads:[~2017-03-14 13:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170313171637eucas1p2d70c4ed7cbd6d088c8c58dc76e1ef722@eucas1p2.samsung.com>
2017-03-13 17:16 ` Denis Khalikov
2017-03-14 8:27 ` Richard Biener
2017-03-14 9:22 ` Matthias Klose
2017-03-14 10:21 ` Denis Khalikov
2017-03-14 13:21 ` Ian Lance Taylor via gcc-patches [this message]
2017-03-14 13:46 ` Denis Khalikov
2017-03-14 13:49 ` Ian Lance Taylor via gcc-patches
2017-03-14 14:30 ` Denis Khalikov
2017-03-14 16:26 ` Ian Lance Taylor via gcc-patches
2017-03-14 17:44 ` Denis Khalikov
2017-03-22 15:29 ` Denis Khalikov
2017-04-12 22:08 ` Jeff Law
2017-05-18 14:23 ` Denis Khalikov
[not found] <CGME20170616153942eucas1p1945271f893265484bbb3991a368bcd92@eucas1p1.samsung.com>
2017-06-16 15:39 ` Denis Khalikov
2017-06-18 14:09 ` Matthias Klose
2017-06-19 8:48 ` Denis Khalikov
2017-06-28 23:59 ` Ian Lance Taylor via gcc-patches
2017-07-01 21:38 ` Denis Khalikov
2017-07-29 20:42 ` Denis Khalikov
2017-09-10 21:11 ` Ian Lance Taylor via gcc-patches
2017-09-11 10:06 ` Denis Khalikov
2017-09-12 14:06 ` Ian Lance Taylor via gcc-patches
2017-09-20 8:54 ` Maxim Ostapenko
2017-09-20 12:33 ` Ian Lance Taylor via gcc-patches
2017-09-20 21:09 ` Ian Lance Taylor via gcc-patches
2017-10-02 11:12 ` Martin Liška
2017-10-02 11:32 ` Jakub Jelinek
2017-10-02 14:01 ` Jakub Jelinek
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=CAKOQZ8xenKq1_1W8d6ZnirySXxPSTwnFt2p0WrvuO4WdMdCPQQ@mail.gmail.com \
--to=gcc-patches@gcc.gnu.org \
--cc=d.khalikov@partner.samsung.com \
--cc=iant@google.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).