On 4/2/20 1:50 AM, Florian Weimer via Libc-alpha wrote: >> What if you move it to GLIBC_PRIVATE? My concern isn't that it's exported >> from the shared library, it's that it's exported at a public version. > > I think it's preferable to duplicate __syscall_error in each shared > object that needs it. It avoids potential strange loops if the lazy > binding code itself ends up calling __syscall_error in an different > object (e.g., from the DSO that implements malloc). > > Maybe we can make this work as long as libc.so uses an internal call, > but it looks tricky. > > Alternatively, we can enable BIND_NOW unconditionally. This seems too big of a trade-off for a seeming small optimization. If you folks feel strongly, I can drop all of this __syscall_error dance. Just let me know what approach to take. _______________________________________________ linux-snps-arc mailing list linux-snps-arc@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/linux-snps-arc
