gcc emit wrong symbols in multiple inheritance case

Hi Dear Gcc developers, When I am trying to build Mozilla with gcc-mingw, I came across the linkage error of undefined symbols in multiple inheritance case. And I have made a simple test case to reproduce the problem. But the test case is still very complex, I think. So, I came down to find th

Re: gcc emit wrong symbols in multiple inheritance case

>When I am trying to build Mozilla with gcc-mingw, I came across > the linkage error of undefined symbols in multiple inheritance case. > And I have made a simple test case to reproduce the problem. But the > test case is still very complex, I think. So, I came down to find the > what are the r

Re: gcc emit wrong symbols in multiple inheritance case

"Bo Yang" <[EMAIL PROTECTED]> writes: > Could anybody give some advice on this? Thanks! The mailing list gcc@gcc.gnu.org is for gcc developers, who mostly do not use cygwin. Try asking on [EMAIL PROTECTED] and/or [EMAIL PROTECTED] Ian

Re: gcc emit wrong symbols in multiple inheritance case

Ian Lance Taylor wrote: "Bo Yang" <[EMAIL PROTECTED]> writes: Could anybody give some advice on this? Thanks! The mailing list gcc@gcc.gnu.org is for gcc developers, who mostly do not use cygwin. Try asking on [EMAIL PROTECTED] and/or [EMAIL PROTECTED] For what it's worth, Bo is my intern

Re: gcc emit wrong symbols in multiple inheritance case

Benjamin Smedberg wrote: > For what it's worth, Bo is my intern in the Google SoC and has traced this > back to being a code-generation error (missed stdcall mangling) in the mingw > backend. I will work with him to narrow the problem and reformulate the > question.. Isn't this

Re: gcc emit wrong symbols in multiple inheritance case

Brian Dessent wrote: Benjamin Smedberg wrote: For what it's worth, Bo is my intern in the Google SoC and has traced this back to being a code-generation error (missed stdcall mangling) in the mingw backend. I will work with him to narrow the problem and reformulate the question.. Isn't this <

Re: gcc emit wrong symbols in multiple inheritance case

On Thu, Jul 31, 2008 at 12:48 AM, Brian Dessent <[EMAIL PROTECTED]> wrote: > Benjamin Smedberg wrote: > >> For what it's worth, Bo is my intern in the Google SoC and has traced this >> back to being a code-generation error (missed stdcall mangling) in the mingw >> backend. I will work with him to n

Re: gcc emit wrong symbols in multiple inheritance case

Bo Yang wrote: > When we produce an exe from a single c++ file, there is no linking > need, so there is no problem. But when we separate the definition and That's not how it works, the linker is always required to produce an executable. > And Obviously, this is not a linker error, it is the prob

Re: gcc emit wrong symbols in multiple inheritance case

On Thu, Jul 31, 2008 at 11:00 PM, Brian Dessent <[EMAIL PROTECTED]> wrote: > Bo Yang wrote: > >> When we produce an exe from a single c++ file, there is no linking >> need, so there is no problem. But when we separate the definition and > > That's not how it works, the linker is always required to