The compiler can't optimize if the symbols are called inter-module either. And seriously, do you REALLY think that any changes the compiler makes at that level will have measurable performance impacts ?. There are good reasons to hide parts of the API that you don't want used by external code - hiding symbols to improve performance is a big stretch.
And there have been linkers which did do a final optimization pass. (OS/2 for example). Peter From: Cristian Rodríguez <crrodrig...@opensuse.org> To: openssl-dev@openssl.org, Date: 26/07/2013 11:55 Subject: Re: [PATCH] libssl: Hide library private symbols Sent by: owner-openssl-...@openssl.org El 25/07/13 21:46, Peter Waltenberg escribió: > Doing this at link time is far easier and can cover all the OS's. Yes, but this is the worst possible way, as the compiler cannot perform optimizations as it does not know that the symbols are hidden. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
