FIX: ggml_time_init() before ggml_time_us() #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
main.cpp fix
Initialize GGML timer before first use to prevent divide‑by‑zero crash on Windows
ggml_time_us() divides by timer_freq, which is set in ggml_time_init().
When main() called ggml_time_us() before that initialization, timer_freq == 0, causing a STATUS_INTEGER_DIVIDE_BY_ZERO (0xC0000094) crash on Windows/MinGW.
at the very top of main().
The first line safely sets timer_freq; the second keeps behaviour identical by recording the start timestamp.
Result
ViT CLI no longer crashes with exit code –1073741676.
--help, inference, and verbose timing output all work as expected on Windows/MinGW, Linux, and macOS.
No other code paths are affected.