## Internal Runtime Utility Functions

### SHA1 Signatures

#### mono_sha1_init

#### mono_sha1_update

#### mono_sha1_get_digest_from_file

#### mono_sha1_get_digest

#### mono_sha1_final

### MD5 Signatures

#### mono_md5_init

#### mono_md5_update

#### mono_md5_get_digest_from_file

#### mono_md5_get_digest

#### mono_md5_final

#### mono_digest_get_public_token

### Hashtables

`GHashTable` is used when you need to store object references into a hashtable, objects stored in a `MonoGHashTable` are properly tracked by the garbage collector.

The `MonoGHashTable` data type has the same API as the GLIB.

#### mono_g_hash_table_destroy

#### mono_g_hash_table_foreach

#### mono_g_hash_table_foreach_remove

#### mono_g_hash_table_insert

#### mono_g_hash_table_lookup

#### mono_g_hash_table_lookup_extended

#### mono_g_hash_table_remove

#### mono_g_hash_table_replace

#### mono_g_hash_table_size

### Memory Pools

Memory pools are a convenient way of tracking memory allocations that are used for one specific task, they are also faster than using the standard memory allocation procedures, as they are designed to be used only by a single thread at a time.

`MonoMemPool` objects are not thread safe, which means that you should not share the objects across multiple threads without providing proper locking around it (unlike `malloc` and `free` which are thread safe).

When a `MonoMemPool` is released with `mono_mempool_destroy` all of the of the memory allocated from that memory pool with `mono_mempool_alloc` and `mono_mempool_alloc0` is released.

#### mono_mempool_new

#### mono_mempool_destroy

#### mono_mempool_alloc

#### mono_mempool_alloc0

#### mono_mempool_invalidate

#### mono_mempool_stats

#### mono_mempool_contains_addr

### Bitsets

MonoBitsets are a set of routines used to manipulate sets of bits.

#### mono_bitset_alloc_size

#### mono_bitset_clear

#### mono_bitset_clear_all

#### mono_bitset_clone

#### mono_bitset_copyto

#### mono_bitset_count

#### mono_bitset_equal

#### mono_bitset_find_first

#### mono_bitset_find_last

#### mono_bitset_find_start

#### mono_bitset_foreach

#### mono_bitset_free

#### mono_bitset_intersection

#### mono_bitset_invert

#### mono_bitset_mem_new

#### mono_bitset_new

#### mono_bitset_set

#### mono_bitset_set_all

#### mono_bitset_size

#### mono_bitset_sub

#### mono_bitset_test

#### mono_bitset_test_bulk

#### mono_bitset_union

#### mono_bitset_find_first_unset

#### mono_bitset_intersection_2

### JIT utilities

#### mono_signbit_double

#### mono_signbit_float

### Function Pointers

To wrap a function pointer into something that the Mono runtime can consume, you should use the mono_create_ftnptr. This is only important if you plan on running on the IA64 architecture. Otherwise you can just use the function pointer address.

#### mono_create_ftnptr

## Notification Interface

This is an internal profiler interface. In general, users would not be using this interface, but would be using the profiler interface.

These methods must be called to notify the profiler of an event that must be recorded. Mono's JIT engine currently calls these routines, but if you are extending Mono in some way these are the methods that you might invoke to notify the profiler of an event.

#### mono_profiler_load

#### mono_profiler_allocation

#### mono_profiler_stat_hit

#### mono_profiler_thread_start

#### mono_profiler_thread_end

#### mono_profiler_appdomain_event

#### mono_profiler_appdomain_loaded

#### mono_profiler_assembly_event

#### mono_profiler_assembly_loaded

#### mono_profiler_class_event

#### mono_profiler_class_loaded

#### mono_profiler_code_transition

#### mono_profiler_method_end_jit

#### mono_profiler_method_enter

#### mono_profiler_method_jit

#### mono_profiler_method_leave

#### mono_profiler_module_event

#### mono_profiler_module_loaded

#### mono_profiler_shutdown

#### mono_profiler_startup

#### mono_profiler_gc_event

#### mono_profiler_gc_heap_resize

#### mono_profiler_stat_hit