2021-03-29 11:39:13 +02:00
|
|
|
|
//! Reading of the rustc metadata for rlibs and dylibs
|
|
|
|
|
|
|
|
|
|
use std::fs::File;
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
use std::io::Write;
|
2021-03-29 11:39:13 +02:00
|
|
|
|
use std::path::Path;
|
|
|
|
|
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
use object::write::{self, StandardSegment, Symbol, SymbolSection};
|
|
|
|
|
use object::{
|
2021-12-19 17:36:48 +01:00
|
|
|
|
elf, pe, Architecture, BinaryFormat, Endianness, FileFlags, Object, ObjectSection,
|
|
|
|
|
SectionFlags, SectionKind, SymbolFlags, SymbolKind, SymbolScope,
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
use snap::write::FrameEncoder;
|
|
|
|
|
|
2021-03-29 11:39:13 +02:00
|
|
|
|
use rustc_data_structures::memmap::Mmap;
|
|
|
|
|
use rustc_data_structures::owning_ref::OwningRef;
|
|
|
|
|
use rustc_data_structures::rustc_erase_owner;
|
|
|
|
|
use rustc_data_structures::sync::MetadataRef;
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
use rustc_metadata::EncodedMetadata;
|
2020-11-14 03:02:03 +01:00
|
|
|
|
use rustc_session::cstore::MetadataLoader;
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
use rustc_session::Session;
|
|
|
|
|
use rustc_target::abi::Endian;
|
2022-05-01 21:45:50 -04:00
|
|
|
|
use rustc_target::spec::{RelocModel, Target};
|
2021-03-29 11:39:13 +02:00
|
|
|
|
|
|
|
|
|
use crate::METADATA_FILENAME;
|
|
|
|
|
|
|
|
|
|
/// The default metadata loader. This is used by cg_llvm and cg_clif.
|
|
|
|
|
///
|
|
|
|
|
/// # Metadata location
|
|
|
|
|
///
|
|
|
|
|
/// <dl>
|
|
|
|
|
/// <dt>rlib</dt>
|
|
|
|
|
/// <dd>The metadata can be found in the `lib.rmeta` file inside of the ar archive.</dd>
|
|
|
|
|
/// <dt>dylib</dt>
|
|
|
|
|
/// <dd>The metadata can be found in the `.rustc` section of the shared library.</dd>
|
|
|
|
|
/// </dl>
|
|
|
|
|
pub struct DefaultMetadataLoader;
|
|
|
|
|
|
|
|
|
|
fn load_metadata_with(
|
|
|
|
|
path: &Path,
|
|
|
|
|
f: impl for<'a> FnOnce(&'a [u8]) -> Result<&'a [u8], String>,
|
|
|
|
|
) -> Result<MetadataRef, String> {
|
2021-05-10 09:49:42 +02:00
|
|
|
|
let file =
|
|
|
|
|
File::open(path).map_err(|e| format!("failed to open file '{}': {}", path.display(), e))?;
|
|
|
|
|
let data = unsafe { Mmap::map(file) }
|
|
|
|
|
.map_err(|e| format!("failed to mmap file '{}': {}", path.display(), e))?;
|
2021-03-29 11:39:13 +02:00
|
|
|
|
let metadata = OwningRef::new(data).try_map(f)?;
|
|
|
|
|
return Ok(rustc_erase_owner!(metadata.map_owner_box()));
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
impl MetadataLoader for DefaultMetadataLoader {
|
|
|
|
|
fn get_rlib_metadata(&self, _target: &Target, path: &Path) -> Result<MetadataRef, String> {
|
|
|
|
|
load_metadata_with(path, |data| {
|
|
|
|
|
let archive = object::read::archive::ArchiveFile::parse(&*data)
|
2021-05-10 09:49:42 +02:00
|
|
|
|
.map_err(|e| format!("failed to parse rlib '{}': {}", path.display(), e))?;
|
2021-03-29 11:39:13 +02:00
|
|
|
|
|
|
|
|
|
for entry_result in archive.members() {
|
2021-05-10 09:49:42 +02:00
|
|
|
|
let entry = entry_result
|
|
|
|
|
.map_err(|e| format!("failed to parse rlib '{}': {}", path.display(), e))?;
|
2021-03-29 11:39:13 +02:00
|
|
|
|
if entry.name() == METADATA_FILENAME.as_bytes() {
|
2021-04-22 11:53:33 -07:00
|
|
|
|
let data = entry
|
|
|
|
|
.data(data)
|
|
|
|
|
.map_err(|e| format!("failed to parse rlib '{}': {}", path.display(), e))?;
|
|
|
|
|
return search_for_metadata(path, data, ".rmeta");
|
2021-03-29 11:39:13 +02:00
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2021-05-10 09:49:42 +02:00
|
|
|
|
Err(format!("metadata not found in rlib '{}'", path.display()))
|
2021-03-29 11:39:13 +02:00
|
|
|
|
})
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
fn get_dylib_metadata(&self, _target: &Target, path: &Path) -> Result<MetadataRef, String> {
|
2021-04-22 11:53:33 -07:00
|
|
|
|
load_metadata_with(path, |data| search_for_metadata(path, data, ".rustc"))
|
2021-03-29 11:39:13 +02:00
|
|
|
|
}
|
|
|
|
|
}
|
2021-04-22 11:53:33 -07:00
|
|
|
|
|
|
|
|
|
fn search_for_metadata<'a>(
|
|
|
|
|
path: &Path,
|
|
|
|
|
bytes: &'a [u8],
|
|
|
|
|
section: &str,
|
|
|
|
|
) -> Result<&'a [u8], String> {
|
2022-02-19 00:48:49 +01:00
|
|
|
|
let Ok(file) = object::File::parse(bytes) else {
|
2021-04-22 11:53:33 -07:00
|
|
|
|
// The parse above could fail for odd reasons like corruption, but for
|
|
|
|
|
// now we just interpret it as this target doesn't support metadata
|
|
|
|
|
// emission in object files so the entire byte slice itself is probably
|
|
|
|
|
// a metadata file. Ideally though if necessary we could at least check
|
|
|
|
|
// the prefix of bytes to see if it's an actual metadata object and if
|
|
|
|
|
// not forward the error along here.
|
2022-02-19 00:48:49 +01:00
|
|
|
|
return Ok(bytes);
|
2021-04-22 11:53:33 -07:00
|
|
|
|
};
|
|
|
|
|
file.section_by_name(section)
|
|
|
|
|
.ok_or_else(|| format!("no `{}` section in '{}'", section, path.display()))?
|
|
|
|
|
.data()
|
|
|
|
|
.map_err(|e| format!("failed to read {} section in '{}': {}", section, path.display(), e))
|
|
|
|
|
}
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
|
2022-04-02 22:54:51 +01:00
|
|
|
|
pub(crate) fn create_object_file(sess: &Session) -> Option<write::Object<'static>> {
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
let endianness = match sess.target.options.endian {
|
|
|
|
|
Endian::Little => Endianness::Little,
|
|
|
|
|
Endian::Big => Endianness::Big,
|
|
|
|
|
};
|
|
|
|
|
let architecture = match &sess.target.arch[..] {
|
|
|
|
|
"arm" => Architecture::Arm,
|
|
|
|
|
"aarch64" => Architecture::Aarch64,
|
|
|
|
|
"x86" => Architecture::I386,
|
|
|
|
|
"s390x" => Architecture::S390x,
|
|
|
|
|
"mips" => Architecture::Mips,
|
|
|
|
|
"mips64" => Architecture::Mips64,
|
|
|
|
|
"x86_64" => {
|
|
|
|
|
if sess.target.pointer_width == 32 {
|
|
|
|
|
Architecture::X86_64_X32
|
|
|
|
|
} else {
|
|
|
|
|
Architecture::X86_64
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
"powerpc" => Architecture::PowerPc,
|
|
|
|
|
"powerpc64" => Architecture::PowerPc64,
|
|
|
|
|
"riscv32" => Architecture::Riscv32,
|
|
|
|
|
"riscv64" => Architecture::Riscv64,
|
|
|
|
|
"sparc64" => Architecture::Sparc64,
|
|
|
|
|
// Unsupported architecture.
|
|
|
|
|
_ => return None,
|
|
|
|
|
};
|
|
|
|
|
let binary_format = if sess.target.is_like_osx {
|
|
|
|
|
BinaryFormat::MachO
|
|
|
|
|
} else if sess.target.is_like_windows {
|
|
|
|
|
BinaryFormat::Coff
|
|
|
|
|
} else {
|
|
|
|
|
BinaryFormat::Elf
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
let mut file = write::Object::new(binary_format, architecture, endianness);
|
2022-06-01 23:13:46 +02:00
|
|
|
|
let e_flags = match architecture {
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
Architecture::Mips => {
|
2022-05-01 21:45:50 -04:00
|
|
|
|
let arch = match sess.target.options.cpu.as_ref() {
|
|
|
|
|
"mips1" => elf::EF_MIPS_ARCH_1,
|
|
|
|
|
"mips2" => elf::EF_MIPS_ARCH_2,
|
|
|
|
|
"mips3" => elf::EF_MIPS_ARCH_3,
|
|
|
|
|
"mips4" => elf::EF_MIPS_ARCH_4,
|
|
|
|
|
"mips5" => elf::EF_MIPS_ARCH_5,
|
|
|
|
|
s if s.contains("r6") => elf::EF_MIPS_ARCH_32R6,
|
|
|
|
|
_ => elf::EF_MIPS_ARCH_32R2,
|
|
|
|
|
};
|
|
|
|
|
// The only ABI LLVM supports for 32-bit MIPS CPUs is o32.
|
|
|
|
|
let mut e_flags = elf::EF_MIPS_CPIC | elf::EF_MIPS_ABI_O32 | arch;
|
|
|
|
|
if sess.target.options.relocation_model != RelocModel::Static {
|
|
|
|
|
e_flags |= elf::EF_MIPS_PIC;
|
|
|
|
|
}
|
|
|
|
|
if sess.target.options.cpu.contains("r6") {
|
|
|
|
|
e_flags |= elf::EF_MIPS_NAN2008;
|
|
|
|
|
}
|
2022-06-01 23:13:46 +02:00
|
|
|
|
e_flags
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
}
|
|
|
|
|
Architecture::Mips64 => {
|
|
|
|
|
// copied from `mips64el-linux-gnuabi64-gcc foo.c -c`
|
2022-01-07 10:47:27 +08:00
|
|
|
|
let e_flags = elf::EF_MIPS_CPIC
|
|
|
|
|
| elf::EF_MIPS_PIC
|
|
|
|
|
| if sess.target.options.cpu.contains("r6") {
|
|
|
|
|
elf::EF_MIPS_ARCH_64R6 | elf::EF_MIPS_NAN2008
|
|
|
|
|
} else {
|
|
|
|
|
elf::EF_MIPS_ARCH_64R2
|
|
|
|
|
};
|
2022-06-01 23:13:46 +02:00
|
|
|
|
e_flags
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
}
|
|
|
|
|
Architecture::Riscv64 if sess.target.options.features.contains("+d") => {
|
|
|
|
|
// copied from `riscv64-linux-gnu-gcc foo.c -c`, note though
|
|
|
|
|
// that the `+d` target feature represents whether the double
|
|
|
|
|
// float abi is enabled.
|
|
|
|
|
let e_flags = elf::EF_RISCV_RVC | elf::EF_RISCV_FLOAT_ABI_DOUBLE;
|
2022-06-01 23:13:46 +02:00
|
|
|
|
e_flags
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
}
|
2022-06-01 23:13:46 +02:00
|
|
|
|
_ => 0,
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
};
|
2022-06-01 23:13:46 +02:00
|
|
|
|
file.flags = FileFlags::Elf { e_flags };
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
Some(file)
|
|
|
|
|
}
|
|
|
|
|
|
2022-02-10 18:43:51 +01:00
|
|
|
|
pub enum MetadataPosition {
|
|
|
|
|
First,
|
|
|
|
|
Last,
|
|
|
|
|
}
|
|
|
|
|
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
// For rlibs we "pack" rustc metadata into a dummy object file. When rustc
|
|
|
|
|
// creates a dylib crate type it will pass `--whole-archive` (or the
|
|
|
|
|
// platform equivalent) to include all object files from an rlib into the
|
|
|
|
|
// final dylib itself. This causes linkers to iterate and try to include all
|
|
|
|
|
// files located in an archive, so if metadata is stored in an archive then
|
|
|
|
|
// it needs to be of a form that the linker will be able to process.
|
|
|
|
|
//
|
|
|
|
|
// Note, though, that we don't actually want this metadata to show up in any
|
|
|
|
|
// final output of the compiler. Instead this is purely for rustc's own
|
|
|
|
|
// metadata tracking purposes.
|
|
|
|
|
//
|
|
|
|
|
// With the above in mind, each "flavor" of object format gets special
|
|
|
|
|
// handling here depending on the target:
|
|
|
|
|
//
|
|
|
|
|
// * MachO - macos-like targets will insert the metadata into a section that
|
|
|
|
|
// is sort of fake dwarf debug info. Inspecting the source of the macos
|
|
|
|
|
// linker this causes these sections to be skipped automatically because
|
|
|
|
|
// it's not in an allowlist of otherwise well known dwarf section names to
|
|
|
|
|
// go into the final artifact.
|
|
|
|
|
//
|
|
|
|
|
// * WebAssembly - we actually don't have any container format for this
|
|
|
|
|
// target. WebAssembly doesn't support the `dylib` crate type anyway so
|
|
|
|
|
// there's no need for us to support this at this time. Consequently the
|
|
|
|
|
// metadata bytes are simply stored as-is into an rlib.
|
|
|
|
|
//
|
|
|
|
|
// * COFF - Windows-like targets create an object with a section that has
|
|
|
|
|
// the `IMAGE_SCN_LNK_REMOVE` flag set which ensures that if the linker
|
|
|
|
|
// ever sees the section it doesn't process it and it's removed.
|
|
|
|
|
//
|
|
|
|
|
// * ELF - All other targets are similar to Windows in that there's a
|
|
|
|
|
// `SHF_EXCLUDE` flag we can set on sections in an object file to get
|
|
|
|
|
// automatically removed from the final output.
|
2022-02-10 18:43:51 +01:00
|
|
|
|
pub fn create_rmeta_file(sess: &Session, metadata: &[u8]) -> (Vec<u8>, MetadataPosition) {
|
2022-02-15 05:58:25 +01:00
|
|
|
|
let Some(mut file) = create_object_file(sess) else {
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
// This is used to handle all "other" targets. This includes targets
|
|
|
|
|
// in two categories:
|
|
|
|
|
//
|
|
|
|
|
// * Some targets don't have support in the `object` crate just yet
|
|
|
|
|
// to write an object file. These targets are likely to get filled
|
|
|
|
|
// out over time.
|
|
|
|
|
//
|
|
|
|
|
// * Targets like WebAssembly don't support dylibs, so the purpose
|
|
|
|
|
// of putting metadata in object files, to support linking rlibs
|
|
|
|
|
// into dylibs, is moot.
|
|
|
|
|
//
|
|
|
|
|
// In both of these cases it means that linking into dylibs will
|
|
|
|
|
// not be supported by rustc. This doesn't matter for targets like
|
|
|
|
|
// WebAssembly and for targets not supported by the `object` crate
|
|
|
|
|
// yet it means that work will need to be done in the `object` crate
|
|
|
|
|
// to add a case above.
|
2022-02-10 18:43:51 +01:00
|
|
|
|
return (metadata.to_vec(), MetadataPosition::Last);
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
};
|
|
|
|
|
let section = file.add_section(
|
|
|
|
|
file.segment_name(StandardSegment::Debug).to_vec(),
|
|
|
|
|
b".rmeta".to_vec(),
|
|
|
|
|
SectionKind::Debug,
|
|
|
|
|
);
|
|
|
|
|
match file.format() {
|
|
|
|
|
BinaryFormat::Coff => {
|
|
|
|
|
file.section_mut(section).flags =
|
2021-12-19 17:36:48 +01:00
|
|
|
|
SectionFlags::Coff { characteristics: pe::IMAGE_SCN_LNK_REMOVE };
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
}
|
|
|
|
|
BinaryFormat::Elf => {
|
2021-12-19 17:36:48 +01:00
|
|
|
|
file.section_mut(section).flags =
|
|
|
|
|
SectionFlags::Elf { sh_flags: elf::SHF_EXCLUDE as u64 };
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
}
|
|
|
|
|
_ => {}
|
|
|
|
|
};
|
|
|
|
|
file.append_section_data(section, metadata, 1);
|
2022-02-10 18:43:51 +01:00
|
|
|
|
(file.write().unwrap(), MetadataPosition::First)
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// Historical note:
|
|
|
|
|
//
|
|
|
|
|
// When using link.exe it was seen that the section name `.note.rustc`
|
|
|
|
|
// was getting shortened to `.note.ru`, and according to the PE and COFF
|
|
|
|
|
// specification:
|
|
|
|
|
//
|
|
|
|
|
// > Executable images do not use a string table and do not support
|
|
|
|
|
// > section names longer than 8 characters
|
|
|
|
|
//
|
|
|
|
|
// https://docs.microsoft.com/en-us/windows/win32/debug/pe-format
|
|
|
|
|
//
|
|
|
|
|
// As a result, we choose a slightly shorter name! As to why
|
|
|
|
|
// `.note.rustc` works on MinGW, see
|
|
|
|
|
// https://github.com/llvm/llvm-project/blob/llvmorg-12.0.0/lld/COFF/Writer.cpp#L1190-L1197
|
|
|
|
|
pub fn create_compressed_metadata_file(
|
|
|
|
|
sess: &Session,
|
|
|
|
|
metadata: &EncodedMetadata,
|
|
|
|
|
symbol_name: &str,
|
|
|
|
|
) -> Vec<u8> {
|
|
|
|
|
let mut compressed = rustc_metadata::METADATA_HEADER.to_vec();
|
|
|
|
|
FrameEncoder::new(&mut compressed).write_all(metadata.raw_data()).unwrap();
|
2022-02-15 05:58:25 +01:00
|
|
|
|
let Some(mut file) = create_object_file(sess) else {
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
return compressed.to_vec();
|
|
|
|
|
};
|
|
|
|
|
let section = file.add_section(
|
|
|
|
|
file.segment_name(StandardSegment::Data).to_vec(),
|
|
|
|
|
b".rustc".to_vec(),
|
2021-12-17 11:26:39 +01:00
|
|
|
|
SectionKind::ReadOnlyData,
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
);
|
2021-12-17 11:26:39 +01:00
|
|
|
|
match file.format() {
|
|
|
|
|
BinaryFormat::Elf => {
|
|
|
|
|
// Explicitly set no flags to avoid SHF_ALLOC default for data section.
|
|
|
|
|
file.section_mut(section).flags = SectionFlags::Elf { sh_flags: 0 };
|
|
|
|
|
}
|
|
|
|
|
_ => {}
|
|
|
|
|
};
|
Use object crate for .rustc metadata generation
We already use the object crate for generating uncompressed .rmeta
metadata object files. This switches the generation of compressed
.rustc object files to use the object crate as well. These have
slightly different requirements in that .rmeta should be completely
excluded from any final compilation artifacts, while .rustc should
be part of shared objects, but not loaded into memory.
The primary motivation for this change is #90326: In LLVM 14, the
current way of setting section flags (and in particular, preventing
the setting of SHF_ALLOC) will no longer work. There are other ways
we could work around this, but switching to the object crate seems
like the most elegant, as we already use it for .rmeta, and as it
makes this independent of the codegen backend. In particular, we
don't need separate handling in codegen_llvm and codegen_gcc.
codegen_cranelift should be able to reuse the implementation as
well, though I have omitted that here, as it is not based on
codegen_ssa.
This change mostly extracts the existing code for .rmeta handling
to allow using it for .rustc as well, and adjust the codegen
infrastructure to handle the metadata object file separately: We
no longer create a backend-specific module for it, and directly
produce the compiled module instead.
This does not fix #90326 by itself yet, as .llvmbc will need to be
handled separately.
2021-12-02 12:24:25 +01:00
|
|
|
|
let offset = file.append_section_data(section, &compressed, 1);
|
|
|
|
|
|
|
|
|
|
// For MachO and probably PE this is necessary to prevent the linker from throwing away the
|
|
|
|
|
// .rustc section. For ELF this isn't necessary, but it also doesn't harm.
|
|
|
|
|
file.add_symbol(Symbol {
|
|
|
|
|
name: symbol_name.as_bytes().to_vec(),
|
|
|
|
|
value: offset,
|
|
|
|
|
size: compressed.len() as u64,
|
|
|
|
|
kind: SymbolKind::Data,
|
|
|
|
|
scope: SymbolScope::Dynamic,
|
|
|
|
|
weak: false,
|
|
|
|
|
section: SymbolSection::Section(section),
|
|
|
|
|
flags: SymbolFlags::None,
|
|
|
|
|
});
|
|
|
|
|
|
|
|
|
|
file.write().unwrap()
|
|
|
|
|
}
|