This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [google] libgcov workaround for weak reference issue (issue 6276043)

From: Xinliang David Li <davidxl at google dot com>
To: Teresa Johnson <tejohnson at google dot com>
Cc: gcc-patches at gcc dot gnu dot org, reply at codereview-hr dot appspotmail dot com
Date: Fri, 1 Jun 2012 14:27:31 -0700
Subject: Re: [google] libgcov workaround for weak reference issue (issue 6276043)
References: <20cf300faf958134bb04c16fb896@google.com> <CAAe5K+UCPyi5-X7uXKOLXp8LtBnoS54oYZBd4+0Sy8fakZqZSg@mail.gmail.com>

ok.

thanks,

David

On Fri, Jun 1, 2012 at 2:26 PM, Teresa Johnson <tejohnson@google.com> wrote:
> Renamed to __gcov_dummy_ref1 and __gcov_dummy_ref2. I'd prefer that
> approach for now to keep the differences with trunk to a minimum.
>
> Thanks,
> Teresa
>
> On Fri, Jun 1, 2012 at 2:18 PM, ?<davidxl@google.com> wrote:
>> Ok with better naming for the dummy function such as
>> '__gcov_dummy_ref1'. Another choice is to let __gcov_flush calls
>> __gcov_dump + __gcov_reset -- but the dump_completed state needs to be
>> saved and restored.
>>
>> David
>>
>> http://codereview.appspot.com/6276043/
>
>
>
> --
> Teresa Johnson?|?Software Engineer?|?tejohnson@google.com?|?408-460-2413

References:
- Re: [google] libgcov workaround for weak reference issue (issue 6276043)
  - From: davidxl
- Re: [google] libgcov workaround for weak reference issue (issue 6276043)
  - From: Teresa Johnson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]