Searched refs:dirty (Results 1 – 5 of 5) sorted by relevance
59 dirty++; in info_main()63 dirty++; in info_main()67 dirty++; in info_main()71 dirty++; in info_main()75 dirty++; in info_main()79 dirty++; in info_main()83 dirty++; in info_main()87 dirty++; in info_main()91 dirty++; in info_main()97 if (dirty > 1) { in info_main()[all …]
73 dirty = date = 1; in version_main()76 dirty = dir = 1; in version_main()79 dirty = engdir = 1; in version_main()82 dirty = moddir = 1; in version_main()85 dirty = cflags = 1; in version_main()88 dirty = options = 1; in version_main()94 dirty = seed = 1; in version_main()97 dirty = version = 1; in version_main()100 dirty = cpuinfo = 1; in version_main()104 dirty = windows = 1; in version_main()[all …]
91 Every time the B<EVP_PKEY> internal key mutates, an internal dirty92 count is incremented. The need for a dirty count is explained further96 the L<EVP_KEYMGMT(3)>, the dirty count is maintained in the B<EVP_PKEY>150 Check if the dirty count for the internal origin key has changed since152 dirty count, which is maintained by the export function.154 If the dirty count has changed, the export cache is cleared.
363 size_t (*dirty) (const EVP_PKEY *pk);366 dirty_cnt() returns the internal key's dirty count.
19537 Note that using the SSL API in certain dirty ways now will result
Completed in 50 milliseconds