Files
Linehu ba16217afe feat: U3 @sealed optional segment marking - phase 2 complete
- UTSM_SEG_F_UNSEALED: plaintext direct-store segments (zero crypto overhead) while keeping capability checks, dirty tracking, intent/commit log and seqlock protocol; default remains sealed
- linker.ld: .sealed output section with __sealed_start/__sealed_end symbols for future static sealed data
- selftest: unsealed segment stores plaintext verifiably + read-back, full SELFTEST PASS (.build_tmp/qemu_serial_u3sealed.log)
- phase 2 (UTSM/UTRW) now complete in ROADMAP_INSANE
2026-10-02 15:30:25 +08:00

44 lines
927 B
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
ENTRY(_start)
PHDRS
{
text PT_LOAD FLAGS(5); /* R-X */
rodata PT_LOAD FLAGS(4); /* R-- */
data PT_LOAD FLAGS(7); /* RWX (SAS-R0) */
}
SECTIONS
{
. = 0xffffffff80000000;
.text : ALIGN(4K) {
*(.text*)
} :text
.rodata : ALIGN(4K) {
*(.limine_requests_start*)
*(.limine_requests*)
*(.limine_requests_end*)
*(.rodata*)
} :rodata
.data : ALIGN(4K) {
*(.data*)
*(COMMON)
} :data
/* U3: @sealed 段标记 —— 用户代码可把静态数据放进 .sealed section
*(__attribute__((section(".sealed")))),UTSM 侧可遍历
* [__sealed_start, __sealed_end) 对该区建立封缄段。未标记数据 0 开销。 */
.sealed : ALIGN(4K) {
__sealed_start = .;
*(.sealed)
*(.sealed.*)
__sealed_end = .;
} :data
.bss : ALIGN(4K) {
*(.bss*)
} :data
}