arch/hexagon/lib/divsi3.S
Source file repositories/reference/linux-study-clean/arch/hexagon/lib/divsi3.S
File Facts
- System
- Linux kernel
- Corpus path
arch/hexagon/lib/divsi3.S- Extension
.S- Size
- 1671 bytes
- Lines
- 68
- Domain
- Architecture Layer
- Bucket
- arch/hexagon
- Inferred role
- Architecture Layer: arch/hexagon
- Status
- atlas-only
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
Dependency Surface
linux/linkage.h
Detected Declarations
function Copyright
Annotated Snippet
#include <linux/linkage.h>
SYM_FUNC_START(__hexagon_divsi3)
{
p0 = cmp.gt(r0,#-1)
p1 = cmp.gt(r1,#-1)
r3:2 = vabsw(r1:0)
}
{
p3 = xor(p0,p1)
r4 = sub(r2,r3)
r6 = cl0(r2)
p0 = cmp.gtu(r3,r2)
}
{
r0 = mux(p3,#-1,#1)
r7 = cl0(r3)
p1 = cmp.gtu(r3,r4)
}
{
r0 = mux(p0,#0,r0)
p0 = or(p0,p1)
if (p0.new) jumpr:nt r31
r6 = sub(r7,r6)
}
{
r7 = r6
r5:4 = combine(#1,r3)
r6 = add(#1,lsr(r6,#1))
p0 = cmp.gtu(r6,#4)
}
{
r5:4 = vaslw(r5:4,r7)
if (!p0) r6 = #3
}
{
loop0(1f,r6)
r7:6 = vlsrw(r5:4,#1)
r1:0 = #0
}
.falign
1:
{
r5:4 = vlsrw(r5:4,#2)
if (!p0.new) r0 = add(r0,r5)
if (!p0.new) r2 = sub(r2,r4)
p0 = cmp.gtu(r4,r2)
}
{
r7:6 = vlsrw(r7:6,#2)
if (!p0.new) r0 = add(r0,r7)
if (!p0.new) r2 = sub(r2,r6)
p0 = cmp.gtu(r6,r2)
}:endloop0
{
if (!p0) r0 = add(r0,r7)
}
{
if (p3) r0 = sub(r1,r0)
jumpr r31
}
SYM_FUNC_END(__hexagon_divsi3)
Annotation
- Immediate include surface: `linux/linkage.h`.
- Detected declarations: `function Copyright`.
- Atlas domain: Architecture Layer / arch/hexagon.
- 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.