public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martin.gieseking at uos dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55543] diamond shaped inheritance involving strings leads to crashing executables (MinGW, 32 bit)
Date: Fri, 30 Nov 2012 15:56:00 -0000	[thread overview]
Message-ID: <bug-55543-4-v6m98XXHWc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55543-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #4 from Martin Gieseking <martin.gieseking at uos dot de> 2012-11-30 15:56:00 UTC ---
Created attachment 28839
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28839
simplified sample code

I simplified the sample code a little bit by removing the static method. The
bug seems to occur only in conjunction with polymorphism and multiple
inheritance. At least, I wasn't able to provoke it with some simpler construct.
So I'm not sure if the failure is actually related to the exception handling
model implemented in the compiler, as the code is supposed to not throw any
exceptions.

As far as I know, mingw64 also uses SjLj, doesn't it? When creating a 64 bit
executable with it, it runs correctly. Only the 32 bit binaries show this
issue.


  parent reply	other threads:[~2012-11-30 15:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30 10:53 [Bug c++/55543] New: " martin.gieseking at uos dot de
2012-11-30 11:09 ` [Bug target/55543] " paolo.carlini at oracle dot com
2012-11-30 11:15 ` ktietz at gcc dot gnu.org
2012-11-30 12:31 ` martin.gieseking at uos dot de
2012-11-30 15:56 ` martin.gieseking at uos dot de [this message]
2012-11-30 16:56 ` ktietz at gcc dot gnu.org
2013-09-10 11:14 ` ktietz at gcc dot gnu.org
2013-09-11  8:21 ` martin.gieseking at uos dot de
2013-09-11  8:24 ` ktietz at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-55543-4-v6m98XXHWc@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).