https://sourceware.org/bugzilla/show_bug.cgi?id=19842
--- Comment #27 from Cary Coutant <ccoutant at gmail dot com> --- > The case where this came up is when we are merging the optimised object, and > were given a weak symbol. The non-LTO object (from -ffat-lto-objects) isn't > loaded if the plugin claims the object. Sorry, I don't follow. Merging? (ld -r?) Merging with what? By "optimized object", do you mean an IR file? Or the result of an LTO link? Who's giving you a weak symbol? Where? Why does it even matter that it's weak? A non-LTO object from -ffat-lto-objects? Not sure what that means, or why you'd want it. Do you mean the non-IR sections in a fat IR file? Plus, we're talking about comdat groups here. We pick the first comdat group we see, which is from the IR file, and discard all the rest. We don't even process the symbols from the discarded ones at all, except to treat them as unsats. It doesn't matter if they're weak. -cary -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
