Module initialization termination function with priorities and (mutable) statics initialization with non const functions.

Minimum rust version required: 1.49

# Functionalities

• [x] Code execution before or after main but after libc and rust runtime has been initialized.

• [x] Mutable and const statics with non const initialization.

• [x] Statics dropable after main exits.

• [x] Zero cost access to statics.

• [x] Priorities on elf plateforms (linux, bsd, etc...) and window.

  Example

  ```rust use static_init::{constructor,destructor,dynamic};

  [constructor]

  unsafe fn do_init(){ } //Care not to use priorities bellow 100 //as those high priorities are used by //the rust runtime. (The lower the number //the higher the priority)

  [constructor(200)]

  unsafe fn do_first(){ }

  [destructor]

  unsafe fn finaly() { }

  [destructor(0)]

  unsafe fn ultimately() { }

  [dynamic]

  static V: Vec = unsafe{vec![1,2,3]};

  [dynamic(init,drop)]

  static mut V1: Vec = unsafe{vec![1,2,3]};

  //Initialized before V1 //then destroyed after V1

  [dynamic(init=142,drop=142)]

  static mut INITANDDROP: Vec = unsafe{vec![1,2,3]};

  fn main(){ asserteq!(V[0],1); unsafe{ asserteq!(V1[2],3); V1[2] = 42; assert_eq!(V1[2], 42); } } ```

  Attributes

  All functions marked with the constructor attribute are run before main is started.

  All function marked with the destructor attribute are run after main has returned.

  Static variables marked with the dynamic attribute can be initialized before main start and optionaly droped after main returns.

  The attributes constructor and destructor works by placing the marked function pointer in dedicated object file sections.

  Priority ranges from 0 to 2<sup>16</sup>-1. The absence of priority is equivalent to 2<sup>16</sup>.

  During program initialization:

  • constructors with priority 0 are the first called;
  • constructors without priority are called last.

  During program termination, the order is reversed:

  • destructors without priority are the first called;
  • destructors with priority 0 are the last called.

Safety

Use of the functionnalities provided by this library are inherently unsafe. During execution of a constructor, any access to variable initialized with a lower or equal priority (higher or equal priority number) will cause undefined behavior. During execution of a destructor any access to variable droped with a lower or equal priority (higher or equal priority number) will cause undefined behavior.

This is actually the reason to be of the priorities: this is the coder own responsability to ensure that no access is performed to lower or equal priorities.

```rust use static_init::dynamic;

#[dynamic] static V1: Vec = unsafe {vec![1,2,3]};

//potential undefined behavior: V1 may not have been initialized yet #[dynamic] static V2: i32 = unsafe {V1[0]};

//undefined behavior, V3 is unconditionnaly initialized before V1 #[dynamic(1000)] static V3: i32 = unsafe {V1[0]};

#[dynamic(1000)] static V4: Vec = unsafe {vec![1,2,3]};

//Good, V5 initialized after V4 #[dynamic(2000)] static V5: i32 = unsafe {V4[0]};

//Good, V6 initialized after V5 and v4 #[dynamic] static V6: i32 = unsafe {*V5+V4[1]};

# fn main(){} ```

# Comparisons against other crates

## lazystatic - lazystatic only provides const statics. - Each access to lazystatic statics costs 2ns on a x86. - lazystatic does not provide priorities. - lazy_static statics initialization is safe.

## ctor - ctor only provides const statics. - ctor does not provide priorities.

# Documentation and details

## Mac - MACH_O specification - GCC source code gcc/config/darwin.c indicates that priorities are not supported.

Initialization functions pointers are placed in section "DATA,modinitfunc" and "DATA,modtermfunc"

## ELF plateforms: - info ld - linker script: ld --verbose - ELF specification

The runtime will run fonctions pointers of section ".initarray" at startup and function pointers in ".finiarray" at program exit. The linker place in the target object file sectio .initarray all sections from the source objects whose name is of the form .initarray.NNNNN in lexicographical order then the .initarray sections of those same source objects. It does equivalently with .finiarray and .fini_array.NNNN sections.

Usage can be seen in gcc source gcc/config/pru.c

Resources of libstdc++ are initialized with priority 100 (see gcc source libstdc++-v3/c++17/defaultresource.h) The rust standard library function that capture the environment and executable arguments is executed at priority 99. Some callbacks constructors and destructors with priority 0 are registered by rust/rtlibrary. Static C++ objects are usually initialized with no priority (TBC). lib-c resources are initialized by the C-runtime before any function in the initarray (whatever the priority) are executed.

## Windows

• this blog post

  At start up, any functions pointer between sections ".CRT$XIA" and ".CRT$XIZ" and then any functions between ".CRT$XCA" and ".CRT$XCZ". It happens that the C library initialization functions pointer are placed in ".CRT$XIU" and C++ statics functions initialization pointers are placed in ".CRT$XCU". At program finish the pointers between sections ".CRT$XPA" and ".CRT$XPZ" are run first then those between ".CRT$XTA" and ".CRT$XTZ".

  Some reverse engineering was necessary to find out a way to implement constructor/destructor priority.

  Contrarily to what is reported in this blog post, msvc linker only performs a lexicographicall ordering of section whose name is of the form "\

  Moreover, it seems that section name of the form \

  So static initialization function pointers are placed in section ".CRT$XCU" and those with a priority p in format!(".CRT$XCTZ{:05}",p). Destructors without priority are placed in ".CRT$XPU" and those with a priority in format!(".CRT$XPTZ{:05}").