fix(DuplicateGlobals): skip unnamed globals and guard against the type mismatch.

[osmandagli]

PR Title

Fix the duplicated global variable names and type mismatch.

PR Description

The original loop in the DuplicateGlobals.cpp file does not control the variable names, and this causes all the unnamed (compiler-generated) variables (e.g., '@3 = internal global i64 0', '@4 = internal global i8 0') to become '@_dup'. This causes a type mismatch error, since the second variable will try to initialize, but the variable type is different than the first one.

Solution

1. Check the variable names at the start of the loop.

if (GV->getName().empty()) {
    continue;
}

2. Check the variable type before initializing

if (Initializer->getType() == GVCopy->getValueType()) {
    GVCopy->setInitializer(Initializer);
}

Summary

Added the necessary checks for all the empty named variables and type mismatches to prevent type mismatch errors.