On 25 May 2017 at 13:06, Kinney, Michael D <michael.d.kin...@intel.com> wrote: > Laszlo and Andrew, > > With the information that has been collected on this thread, I > still think this patch in its original form is a good change > to resolve the this one specific duplicate symbol issue for all > tool chains. 'static' can not be mixed with > GLOBAL_REMOVE_IF_UNREFERENCED for MSFT tool chains, so renaming > the global variable is the easiest way to remove the duplicate. >
GLOBAL_REMOVE_IF_UNREFERENCED itself is problematic imo. I think it was Felix who reported on this recently? STATIC is really the only sensible way to deal with this for symbols that are only referenced by a single compilation unit. > I will continue to work on ways to detect duplicate symbols for > all tool chains and will enter a Bugzilla issue to for that > feature. > > In addition, the idea of detecting if a library is exporting more > than the library class defines is another good feature to consider > and I will enter a Bugzilla issue for that one as well. > > If we can find ways to both restrict the symbols exported by a > library and strip all symbols that are unused, then we can have > additional Bugzilla issues to perform that clean up on each > library instance that is exporting more than the library class. > A static library is nothing more than an archive containing a collection of object files. Sadly, that implies that we cannot distinguish between symbols that may only be referenced by other objects in the same static library and symbols that are exported to the library client. _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
