9f33fc63c6
Instead, each module defines a static CRYPTO_EX_DATA_CLASS to hold the values. This makes CRYPTO_cleanup_all_ex_data a no-op as spreading the CRYPTO_EX_DATA_CLASSes across modules (and across crypto and ssl) makes cleanup slightly trickier. We can make it do something if needbe, but it's probably not worth the trouble. Change-Id: Ib6f6fd39a51d8ba88649f0fa29c66db540610c76 Reviewed-on: https://boringssl-review.googlesource.com/4375 Reviewed-by: Adam Langley <agl@google.com> |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| ec_asn1.c | ||
| ec_key.c | ||
| ec_montgomery.c | ||
| ec_test.c | ||
| ec.c | ||
| example_mul.c | ||
| internal.h | ||
| oct.c | ||
| simple.c | ||
| wnaf.c | ||