Re: gcc generated memcpy calls symbol version

2018-01-30 Thread Tom Mason
on a system with glibc 2.13 installed. If I force it to an earlier version however, then it'll work just fine. On Jan 29, 2018 9:05 PM, "Andi Kleen" wrote: > Tom Mason writes: > > > Is there any way for me to force the version for these symbols aswell? > > It see

Re: gcc generated memcpy calls symbol version

2018-01-27 Thread Tom Mason
Actually, never mind, it's working fine: https://gist.github.com/wheybags/b7e4152daf76c72503e9e1f52f3dca3d and I have some other problem. On Fri, Jan 26, 2018 at 9:22 PM, H.J. Lu wrote: > On Fri, Jan 26, 2018 at 1:17 PM, Tom Mason wrote: > > I'm not entirely sure I understa

Re: gcc generated memcpy calls symbol version

2018-01-26 Thread Tom Mason
:p On Fri, Jan 26, 2018 at 8:37 PM, H.J. Lu wrote: > On Fri, Jan 26, 2018 at 12:29 PM, Tom Mason wrote: > > Hi, > > I've got a project here: https://github.com/wheybags/ > glibc_version_header > > which uses .symver directives to link to a specified version of glibc

gcc generated memcpy calls symbol version

2018-01-26 Thread Tom Mason
re that I can disable the whole mechanism with -freestanding, but I don't want to cripple the optimiser. Regards, Tom Mason