Skip to content

v: improved -skip-unused #7893

v: improved -skip-unused

v: improved -skip-unused #7893

Triggered via pull request November 14, 2024 18:03
Status Cancelled
Total duration 16m 53s
Artifacts

linux_ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 10 warnings
tcc
Process completed with exit code 1.
gcc
Canceling since a higher priority waiting request for 'CI Linux-refs/pull/22856/merge' exists
gcc
The operation was canceled.
clang
Canceling since a higher priority waiting request for 'CI Linux-refs/pull/22856/merge' exists
clang
The operation was canceled.
tcc: vlib/builtin/map_test.v#L214
accessing a pointer map value requires an `or {}` block outside `unsafe`
tcc: vlib/builtin/map_test.v#L214
accessing map value that contain pointers requires an `or {}` block outside `unsafe`
tcc: vlib/builtin/map_test.v#L217
accessing a pointer map value requires an `or {}` block outside `unsafe`
tcc: vlib/builtin/map_test.v#L217
accessing map value that contain pointers requires an `or {}` block outside `unsafe`
tcc: vlib/builtin/map_test.v#L226
accessing a pointer map value requires an `or {}` block outside `unsafe`
tcc: vlib/builtin/map_test.v#L226
accessing map value that contain pointers requires an `or {}` block outside `unsafe`
tcc: vlib/builtin/map_test.v#L671
accessing a pointer map value requires an `or {}` block outside `unsafe`
tcc: vlib/builtin/map_test.v#L671
accessing map value that contain pointers requires an `or {}` block outside `unsafe`
tcc: vlib/builtin/map_test.v#L672
accessing a pointer map value requires an `or {}` block outside `unsafe`
tcc: vlib/builtin/map_test.v#L672
accessing map value that contain pointers requires an `or {}` block outside `unsafe`