From 2fbf9cb25e930e2df86d05e0f7f707e69bae2b1f Mon Sep 17 00:00:00 2001 From: Philip Herron Date: Sat, 29 Jan 2022 14:55:51 +0000 Subject: Track the cratenum for the respective canonical path This means we can get the crate name to squash the warning in the V0 symbol mangling scheme. --- gcc/rust/backend/rust-mangle.cc | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'gcc/rust/backend/rust-mangle.cc') diff --git a/gcc/rust/backend/rust-mangle.cc b/gcc/rust/backend/rust-mangle.cc index 2c86488..eaf7814 100644 --- a/gcc/rust/backend/rust-mangle.cc +++ b/gcc/rust/backend/rust-mangle.cc @@ -252,12 +252,16 @@ legacy_mangle_item (const TyTy::BaseType *ty, static std::string v0_mangle_item (const TyTy::BaseType *ty, const Resolver::CanonicalPath &path) { - std::string mangled; + // we can get this from the canonical_path + auto mappings = Analysis::Mappings::get (); + std::string crate_name; + bool ok = mappings->get_crate_name (path.get_crate_num (), crate_name); + rust_assert (ok); + std::string mangled; // FIXME: Add real algorithm once all pieces are implemented auto ty_prefix = v0_type_prefix (ty); - // crate name must be assumed to be part of the canonical path - // v0_add_identifier (mangled, crate_name); + v0_add_identifier (mangled, crate_name); v0_add_disambiguator (mangled, 62); gcc_unreachable (); -- cgit v1.1