rust/zerocopy/benches/extend_vec_zeroed.x86-64

File Facts

System

Linux kernel

Corpus path

rust/zerocopy/benches/extend_vec_zeroed.x86-64

Extension

.x86-64

Size

1013 bytes

Lines

61

Domain

Rust Kernel Layer

Bucket

Rust API Membrane

Inferred role

Rust Kernel Layer: Rust API Membrane

Status

atlas-only

Why This File Exists

Rust-side wrappers and abstractions around kernel C APIs, ownership contracts, allocation, synchronization, and module integration.

• Rust-side wrappers and abstractions around kernel C APIs, ownership contracts, allocation, synchronization, and module integration.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

bench_extend_vec_zeroed:
	push r15
	push r14
	push r13
	push r12
	push rbx
	sub rsp, 32
	mov rbx, rdi
	mov rax, qword ptr [rdi]
	mov r12, qword ptr [rdi + 16]
	mov rcx, rax
	sub rcx, r12
	cmp rsi, rcx
	jbe .LBB6_3
	mov r15, r12
	add r15, rsi
	jae .LBB6_6
.LBB6_2:
	xor eax, eax
	jmp .LBB6_5
.LBB6_3:
	mov rax, qword ptr [rbx + 8]
	lea r15, [r12 + rsi]
.LBB6_4:
	lea rcx, [r12 + 2*r12]
	lea rdi, [rax + 2*rcx]
	add rsi, rsi
	lea rdx, [rsi + 2*rsi]
	xor esi, esi
	call qword ptr [rip + memset@GOTPCREL]
	mov qword ptr [rbx + 16], r15
	mov al, 1
.LBB6_5:
	add rsp, 32
	pop rbx
	pop r12
	pop r13
	pop r14
	pop r15
	ret
.LBB6_6:
	mov r13, rsi
	lea rcx, [rax + rax]
	cmp r15, rcx
	cmova rcx, r15
	cmp rcx, 5
	mov r14d, 4
	cmovae r14, rcx
	mov rdx, qword ptr [rbx + 8]
	lea rdi, [rsp + 8]
	mov rsi, rax
	mov rcx, r14
	call <alloc::raw_vec::RawVecInner>::finish_grow
	cmp dword ptr [rsp + 8], 1
	je .LBB6_2
	mov rax, qword ptr [rsp + 16]
	mov qword ptr [rbx + 8], rax
	mov qword ptr [rbx], r14
	mov rsi, r13
	jmp .LBB6_4

Annotation

• Atlas domain: Rust Kernel Layer / Rust API Membrane.
• Implementation status: atlas-only.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.