On Mon, 20 Jan 2020, H.J. Lu wrote: > > Bare IFUNC's don't seem to have this restriction. Why do we want to > > constrain target clones this way? > > > > foo's resolver acts as foo. It should have the same visibility as foo. What do you mean by that? From the implementation standpoint, there's two symbols of different type with the same value. There's no problem allowing one of them have local binding and the other have global binding. Is there something special about target clones that doesn't come into play with ifuncs? Alexander
- [PATCH] Make target_clones resolver fn static. Martin Liška
- Re: [PATCH] Make target_clones resolver fn static. Richard Biener
- Re: [PATCH] Make target_clones resolver fn stat... H.J. Lu
- Re: [PATCH] Make target_clones resolver fn ... Alexander Monakov
- Re: [PATCH] Make target_clones resolver... H.J. Lu
- Re: [PATCH] Make target_clones res... Alexander Monakov
- Re: [PATCH] Make target_clones... H.J. Lu
- Re: [PATCH] Make target_cl... Alexander Monakov
- Re: [PATCH] Make target_cl... H.J. Lu
- Re: [PATCH] Make target_cl... Richard Biener
- Re: [PATCH] Make target_cl... Martin Liška
- Re: [PATCH] Make target_cl... Richard Biener
- Re: [PATCH] Make target_cl... Martin Liška
- Re: [PATCH] Make target_cl... Alexander Monakov
- Re: [PATCH] Make target_cl... Martin Liška
- Re: [PATCH] Make target_cl... Jeff Law
- Re: [PATCH] Make target_cl... Martin Liška