On Sat, Mar 02, 2013 at 09:23:15PM +0100, Dimitry Andric wrote:
> On 2013-03-02 18:52, Andriy Gapon wrote:
> > on 02/03/2013 19:35 Andriy Gapon said the following:
> >> Now, I am not quite sure why ctfconvert skips bpobj_iterate_impl in the
> >> clang-generated code. Seems like some sort of a bug
On 2013-03-02 18:52, Andriy Gapon wrote:
on 02/03/2013 19:35 Andriy Gapon said the following:
Now, I am not quite sure why ctfconvert skips bpobj_iterate_impl in the
clang-generated code. Seems like some sort of a bug in ctfconvert.
It seems that gcc and clang put different names for symbol o
on 02/03/2013 19:35 Andriy Gapon said the following:
> Now, I am not quite sure why ctfconvert skips bpobj_iterate_impl in the
> clang-generated code. Seems like some sort of a bug in ctfconvert.
It seems that gcc and clang put different names for symbol of type FILE:
clang:
readelf -a -W /usr/ob
I observe the following problem.
There are two tiny wrapper functions around a larger implementation function:
int
bpobj_iterate(bpobj_t *bpo, bpobj_itor_t func, void *arg, dmu_tx_t *tx)
{
return (bpobj_iterate_impl(bpo, func, arg, tx, B_TRUE));
}
int
bpobj_iterate_nofree(bpobj_t *bpo, bp
4 matches
Mail list logo
