From: "Ian Lance Taylor via gcc-patches" <gcc-patches@gcc.gnu.org>
To: Tom de Vries <tdevries@suse.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, Ian Lance Taylor <ian@airs.com>
Subject: Re: [PATCH 1/5][libbacktrace] Factor out backtrace_vector_free
Date: Thu, 29 Nov 2018 18:17:00 -0000 [thread overview]
Message-ID: <CAKOQZ8z3Cnw_M10RPeLpQjELm-0BYPo2ojzsebBi7RBkOCyAJg@mail.gmail.com> (raw)
In-Reply-To: <1ff25d02-c383-d8db-1673-eb61416ade8a@suse.de>
On Thu, Nov 29, 2018 at 4:33 AM, Tom de Vries <tdevries@suse.de> wrote:
> On 29-11-18 00:26, Ian Lance Taylor wrote:
>> On Wed, Nov 28, 2018 at 3:15 PM, Tom de Vries <tdevries@suse.de> wrote:
>>>
>>> this patch factors out new function backtrace_vector_free.
>>>
>>> Bootstrapped and reg-tested on x86_64.
>>>
>>> OK for trunk?
>>
>> We should only add new files if we really absolutely must, as this
>> package is copied around to a lot of places (e.g.,
>> libsanitizer/libbacktrace) and adding files here requires
>> modifications in all those places.
>>
>
> I see, thanks for the explanation.
>
> How about his patch? It does not add a file, though it does add an
> external function which requires a rename in libsanitizer/libbacktrace
> (I don't know whether that requires changes in any other places).
>
> [ Also, it inlines backtrace-vector.c into alloc.c and mmap.c, so it
> duplicates code. If that is not acceptable, I could move it to
> internal.h as static inline or static ATTRIBUTE_UNUSED. ]
Yes, let's just use a static inline function or a macro. Thanks.
Ian
next prev parent reply other threads:[~2018-11-29 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 23:16 Tom de Vries
2018-11-28 23:26 ` Ian Lance Taylor via gcc-patches
2018-11-29 12:33 ` Tom de Vries
2018-11-29 18:17 ` Ian Lance Taylor via gcc-patches [this message]
2018-11-30 9:02 ` Tom de Vries
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=CAKOQZ8z3Cnw_M10RPeLpQjELm-0BYPo2ojzsebBi7RBkOCyAJg@mail.gmail.com \
--to=gcc-patches@gcc.gnu.org \
--cc=ian@airs.com \
--cc=iant@google.com \
--cc=tdevries@suse.de \
/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).