On Wed, Jun 27, 2018 at 05:25:17PM +0100, Nick Clifton wrote: > > Nick, this looks like an annobin bug. This is really, really problematic from an ABI perspective. > > OK - so if I change annobin so that it creates its own function start symbol, > eg libxsmm_crc32_u64_start and then it references this symbol in the .weak What if the TU already uses libxsmm_crc32_u64_start for something completely different? If annobin wants to add its own symbols, they must be not in the user namespace (so need to include some prefix with . char at best) and better it should ensure that such symbols aren't exported from shared libraries or binaries it creates either. Jakub _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/24UFA3U5UX4XEHFFP6EBKHD3R5NLDHTV/
