1 // This defines a base target-configuration for native UEFI systems. The UEFI specification has
2 // quite detailed sections on the ABI of all the supported target architectures. In almost all
3 // cases it simply follows what Microsoft Windows does. Hence, whenever in doubt, see the MSDN
5 // UEFI uses COFF/PE32+ format for binaries. All binaries must be statically linked. No dynamic
6 // linker is supported. As native to COFF, binaries are position-dependent, but will be relocated
7 // by the loader if the pre-chosen memory location is already in use.
8 // UEFI forbids running code on anything but the boot-CPU. No interrupts are allowed other than
9 // the timer-interrupt. Device-drivers are required to use polling-based models. Furthermore, all
10 // code runs in the same environment, no process separation is supported.
12 use crate::spec::{LinkArgs, LinkerFlavor, LldFlavor, PanicStrategy, TargetOptions};
13 use std::default::Default;
15 pub fn opts() -> TargetOptions {
16 let pre_link_args_msvc = vec![
17 // Suppress the verbose logo and authorship debugging output, which would needlessly
18 // clog any log files.
19 "/NOLOGO".to_string(),
20 // UEFI is fully compatible to non-executable data pages. Tell the compiler that
21 // non-code sections can be marked as non-executable, including stack pages. In fact,
22 // firmware might enforce this, so we better let the linker know about this, so it
23 // will fail if the compiler ever tries placing code on the stack (e.g., trampoline
24 // constructs and alike).
25 "/NXCOMPAT".to_string(),
26 // Non-standard subsystems have no default entry-point in PE+ files. We have to define
27 // one. "efi_main" seems to be a common choice amongst other implementations and the
29 "/entry:efi_main".to_string(),
30 // COFF images have a "Subsystem" field in their header, which defines what kind of
31 // program it is. UEFI has 3 fields reserved, which are EFI_APPLICATION,
32 // EFI_BOOT_SERVICE_DRIVER, and EFI_RUNTIME_DRIVER. We default to EFI_APPLICATION,
33 // which is very likely the most common option. Individual projects can override this
34 // with custom linker flags.
35 // The subsystem-type only has minor effects on the application. It defines the memory
36 // regions the application is loaded into (runtime-drivers need to be put into
37 // reserved areas), as well as whether a return from the entry-point is treated as
38 // exit (default for applications).
39 "/subsystem:efi_application".to_string(),
41 let mut pre_link_args = LinkArgs::new();
42 pre_link_args.insert(LinkerFlavor::Msvc, pre_link_args_msvc.clone());
43 pre_link_args.insert(LinkerFlavor::Lld(LldFlavor::Link), pre_link_args_msvc);
46 dynamic_linking: false,
48 disable_redzone: true,
49 exe_suffix: ".efi".to_string(),
50 allows_weak_linkage: false,
51 panic_strategy: PanicStrategy::Abort,
54 emit_debug_gdb_scripts: false,
56 linker: Some("rust-lld".to_string()),
57 lld_flavor: LldFlavor::Link,