> Hi.
>
> Using priority {cd}tors on a target that does not support that can cause
> failures (see the PR).
> Apart from that, I decided to use priority 100 for both gcov_init and
> gcov_exit functions as
> the reserved range includes priority 100. Moreover, I enhanced test-cases we
> have.
>
PING^2
On 11/14/2016 01:12 PM, Martin Liška wrote:
> PING^1
>
> On 10/31/2016 01:13 PM, Martin Liška wrote:
>> On 10/31/2016 11:07 AM, Rainer Orth wrote:
>>> Hi Martin,
>>>
Using priority {cd}tors on a target that does not support that can cause
failures (see the PR).
Apart from
PING^1
On 10/31/2016 01:13 PM, Martin Liška wrote:
> On 10/31/2016 11:07 AM, Rainer Orth wrote:
>> Hi Martin,
>>
>>> Using priority {cd}tors on a target that does not support that can cause
>>> failures (see the PR).
>>> Apart from that, I decided to use priority 100 for both gcov_init and
>>>
On 10/31/2016 11:07 AM, Rainer Orth wrote:
> Hi Martin,
>
>> Using priority {cd}tors on a target that does not support that can cause
>> failures (see the PR).
>> Apart from that, I decided to use priority 100 for both gcov_init and
>> gcov_exit functions as
>> the reserved range includes
Hi Martin,
> Using priority {cd}tors on a target that does not support that can cause
> failures (see the PR).
> Apart from that, I decided to use priority 100 for both gcov_init and
> gcov_exit functions as
> the reserved range includes priority 100. Moreover, I enhanced test-cases
> we have.
Hi.
Using priority {cd}tors on a target that does not support that can cause
failures (see the PR).
Apart from that, I decided to use priority 100 for both gcov_init and gcov_exit
functions as
the reserved range includes priority 100. Moreover, I enhanced test-cases we
have.
Patch can
