[Bug target/27067] Compile errors with multiple inheritance where the stdcall attribute is applied to virtual functions.

2007-05-08 Thread angray at beeb dot net 


--- Comment #12 from angray at beeb dot net  2007-05-08 15:07 ---
(In reply to comment #11)
 MSC includes the calling convention as part of its C++ name mangling.  Would
 this bug be easier to solve if the calling convention was also included as 
 part
 of the C++ name mangling in GCC, instead of done afterwards?  If so, it might
 be worth this small ABI breaking change in some future release of MinGW.

Does this bug effect Firefox and Thunderbirds XPCOM ?

Aaron


-- 

angray at beeb dot net changed:

   What|Removed |Added

 CC||angray at beeb dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27067

[Bug target/27067] Compile errors with multiple inheritance where the stdcall attribute is applied to virtual functions.

2007-05-08 Thread angray at beeb dot net 


--- Comment #14 from angray at beeb dot net  2007-05-08 22:02 ---
(In reply to comment #13)
 Subject: Re:  Compile errors with multiple inheritance where
  the stdcall attribute is applied to virtual functions.
 rridge at csclub dot uwaterloo dot ca wrote:
  --- Comment #11 from rridge at csclub dot uwaterloo dot ca  2007-05-08 
  12:25 ---
  MSC includes the calling convention as part of its C++ name mangling.  Would
  this bug be easier to solve if the calling convention was also included as 
  part
  of the C++ name mangling in GCC, instead of done afterwards?  If so, it 
  might
  be worth this small ABI breaking change in some future release of MinGW.
 I think that would be fine, from a C++ perspective.

If indeed XPCOM is dependant upon this then making an ABI namemangling change
would break Firefox and Thunderbird addons.

Aaron


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27067