Lines Matching +full:work +full:- +full:around

5 (NOT a "zephyr.strip" intended for grub/multiboot loading -- we need
18 appropriate locations at startup, clear any zero-filled (BSS, etc...)
32 The code and link environment here is non-obvious.  The simple rules
39 work fine and then fail inexplicably at runtime with a garbage
45 Linux toolchain.  EFI binaries are relocatable PE-COFF files --
50 independent code.  Non-static global variables and function addresses
52 time by a system binary (ld-linux.so).  But there is no ld-linux.so in
57 via the x86_64 RIP-relative addressing mode and doesn't rely on any
59 the compiler (not the linker) knows a-priori will never be in
61 symbols work.
63 You might ask: why build a position-independent executable in the
64 first place?  Why not just link to a specific address?  The PE-COFF
68 arbitrary locations in memory.  I couldn't make it work, basically.
75 a IP-relative addressing mode, so we'd have to do some kind of
77 a proper PE-COFF toolchain.
82 systems I've tried, EFI uses memory near the top of 32-bit-accessible
85 could control the Zephyr mapping addresses per-platform if needed to
86 sneak around EFI areas.  But the Zephyr loader should at least detect