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 - hid
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.
___
Doing this at link time is far easier and can cover all the OS's.
Static doesn't work for symbols that are called inter-module but which
shouldn't be in the public API and GCC specific constructs only work for -
well, GCC.
libeay.num and ssleay.num already list all the public symbols. Parse those
I've submitted a patch in 2007 to make as much as possible static,
but it never got applied, so I never bothered writing a patch to
make the rest hidden. I think making things static is even better
than hiding them, and should work on all platforms. It's just
that you can't making everything that
On Fri, Jul 19, 2013, Leon Brits wrote:
> Hi all,
>
> I want/need to create a PKCS12 file which contains more than one key pair and
> some CA certs. As far as I understand from the spec this is possible, but the
> OpenSSL API does not seem to support this, since only the CAs can be passed
> as
