Skip to content

Clarify why SGX code specifies linkage/symbol names for certain statics #155659

Clarify why SGX code specifies linkage/symbol names for certain statics

Clarify why SGX code specifies linkage/symbol names for certain statics #155659

Triggered via pull request April 14, 2025 11:38
Status Success
Total duration 1h 4m 20s
Artifacts 1

ci.yml

on: pull_request
Calculate job matrix
45s
Calculate job matrix
Matrix: job
bors build finished
0s
bors build finished
Fit to window
Zoom out
Zoom in

Annotations

8 errors
PR - x86_64-gnu-tools
unexpected closing delimiter: `}`
PR - x86_64-gnu-tools
this file contains an unclosed delimiter
PR - x86_64-gnu-tools
this file contains an unclosed delimiter
PR - x86_64-gnu-tools
lifetimes cannot start with a number
PR - x86_64-gnu-tools
unexpected closing delimiter: `}`
PR - x86_64-gnu-tools
missing type for `static` item
PR - x86_64-gnu-tools
unexpected `if` in the condition expression
PR - x86_64-gnu-tools
mismatched closing delimiter: `}`

Artifacts

Produced during runtime
Name Size Digest
doc-139795-8dc77329 Expired
17.2 MB
sha256:1e7517dac108916cf6e73596d4a06c991be340615c1497a8bd3f6ca15b60ba5b