tools/objtool/arch/loongarch/include/arch/elf.h

Source file repositories/reference/linux-study-clean/tools/objtool/arch/loongarch/include/arch/elf.h

File Facts

System: Linux kernel
Corpus path: tools/objtool/arch/loongarch/include/arch/elf.h
Extension: .h
Size: 860 bytes
Lines: 38
Domain: Support Tooling And Documentation
Bucket: tools
Inferred role: Support Tooling And Documentation: implementation source
Status: source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

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

#ifndef _OBJTOOL_ARCH_ELF_H
#define _OBJTOOL_ARCH_ELF_H

/*
 * See the following link for more info about ELF Relocation types:
 * https://loongson.github.io/LoongArch-Documentation/LoongArch-ELF-ABI-EN.html#_relocations
 */
#ifndef R_LARCH_NONE
#define R_LARCH_NONE		0
#endif
#ifndef R_LARCH_32
#define R_LARCH_32		1
#endif
#ifndef R_LARCH_64
#define R_LARCH_64		2
#endif
#ifndef R_LARCH_32_PCREL
#define R_LARCH_32_PCREL	99
#endif
#ifndef R_LARCH_64_PCREL
#define R_LARCH_64_PCREL	109
#endif

#ifndef EM_LOONGARCH
#define EM_LOONGARCH		258
#endif

#define R_NONE			R_LARCH_NONE
#define R_ABS32			R_LARCH_32
#define R_ABS64			R_LARCH_64
#define R_DATA32		R_LARCH_32_PCREL
#define R_DATA64		R_LARCH_32_PCREL
#define R_TEXT32		R_LARCH_32_PCREL
#define R_TEXT64		R_LARCH_32_PCREL

#endif /* _OBJTOOL_ARCH_ELF_H */

Annotation

Atlas domain: Support Tooling And Documentation / tools.
Implementation status: source implementation candidate.

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.