2b63addf6a
The newer clang-cl is unhappy about the tautological comparison on Windows, but the comparison itself is unnecessary anyway, since the values will never exceed uint32_t. I think the reason it's not firing elsewhere is because on other 64-bit platforms, it is not tautological because long is 64-bit. On other 32-bit platforms, I'm not sure we actually have a standalone trunk clang builder right now. Update-Note: UTF8_getc and UTF8_putc were unexported. No one appears to be calling them. (We're a crypto library, not a Unicode library.) Change-Id: I0949ddea3131dca5f55d04e672c3ccf2915c41ab Reviewed-on: https://boringssl-review.googlesource.com/23844 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> |
||
---|---|---|
.. | ||
a_digest.c | ||
a_sign.c | ||
a_strex.c | ||
a_verify.c | ||
algorithm.c | ||
asn1_gen.c | ||
by_dir.c | ||
by_file.c | ||
charmap.h | ||
CMakeLists.txt | ||
i2d_pr.c | ||
internal.h | ||
make_many_constraints.go | ||
many_constraints.pem | ||
many_names1.pem | ||
many_names2.pem | ||
many_names3.pem | ||
rsa_pss.c | ||
some_names1.pem | ||
some_names2.pem | ||
some_names3.pem | ||
t_crl.c | ||
t_req.c | ||
t_x509.c | ||
t_x509a.c | ||
vpm_int.h | ||
x509_att.c | ||
x509_cmp.c | ||
x509_d2.c | ||
x509_def.c | ||
x509_ext.c | ||
x509_lu.c | ||
x509_obj.c | ||
x509_r2x.c | ||
x509_req.c | ||
x509_set.c | ||
x509_test.cc | ||
x509_trs.c | ||
x509_txt.c | ||
x509_v3.c | ||
x509_vfy.c | ||
x509_vpm.c | ||
x509.c | ||
x509cset.c | ||
x509name.c | ||
x509rset.c | ||
x509spki.c | ||
x_algor.c | ||
x_all.c | ||
x_attrib.c | ||
x_crl.c | ||
x_exten.c | ||
x_info.c | ||
x_name.c | ||
x_pkey.c | ||
x_pubkey.c | ||
x_req.c | ||
x_sig.c | ||
x_spki.c | ||
x_val.c | ||
x_x509.c | ||
x_x509a.c |