This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/53930] bug in linker
- From: "bespalovdn at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 12 Jul 2012 07:59:03 +0000
- Subject: [Bug c++/53930] bug in linker
- Auto-submitted: auto-generated
- References: <bug-53930-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53930
Dmitry Bespalov <bespalovdn at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
--- Comment #4 from Dmitry Bespalov <bespalovdn at gmail dot com> 2012-07-12 07:59:03 UTC ---
Andrew,
Yes, I have two different definitions of "A" struct. But they are defined in
different cpp files, so actually linker should not have ambiguity, which one to
pick up, since the names of these structs for linker should be something like
"file1.A" and "file2.A".
If this rule is broken, then result should be completely anarchy. Suppose we
have 1000 files in the project - there is no guarantee that all the structs
defined in cpps have unique names. And rule "which one to puck up is depend on
link order" or "it could be any random one" are sounds scary to me.