public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Franz.Sirl-kernel@lauterbach.com
To: gcc-gnats@gcc.gnu.org
Cc: stefan@space.twc.de
Subject: c++/3061: kde2/artsd miscompilation (part 2)
Date: Tue, 05 Jun 2001 15:46:00 -0000	[thread overview]
Message-ID: <20010605224419.4977.qmail@sourceware.cygnus.com> (raw)

>Number:         3061
>Category:       c++
>Synopsis:       kde2/artsd miscompilation (part 2)
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 05 15:46:05 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Franz.Sirl-kernel@lauterbach.com
>Release:        gcc version 3.0 20010605 (prerelease)
>Organization:
>Environment:
x86-linux-gnu, ppc-linux-gnu
>Description:
The attached code segfaults on execution if compiled with the current gcc-3.0. gcc-2.95 works fine.
>How-To-Repeat:
class A_base {
public:
        virtual void foo() { }
};
class A_skel : virtual public A_base { };
 
class B_base : virtual public A_base { };
class B_skel : virtual public B_base, virtual public A_skel { };
 
class C_base : virtual public B_base { };
class C_skel : virtual public C_base, virtual public B_skel { };
 
class D_base : virtual public C_base { };
class D_skel : virtual public D_base, virtual public C_skel { };
 
class D_impl : virtual public D_skel { };
 
int main()
{
        D_impl i;
}
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-c++src; name="gcc3-arts-testcase2.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="gcc3-arts-testcase2.cc"

Y2xhc3MgQV9iYXNlIHsKcHVibGljOgoJdmlydHVhbCB2b2lkIGZvbygpIHsgfQp9OwpjbGFzcyBB
X3NrZWwgOiB2aXJ0dWFsIHB1YmxpYyBBX2Jhc2UgeyB9OwoKY2xhc3MgQl9iYXNlIDogdmlydHVh
bCBwdWJsaWMgQV9iYXNlIHsgfTsKY2xhc3MgQl9za2VsIDogdmlydHVhbCBwdWJsaWMgQl9iYXNl
LCB2aXJ0dWFsIHB1YmxpYyBBX3NrZWwgeyB9OwoKY2xhc3MgQ19iYXNlIDogdmlydHVhbCBwdWJs
aWMgQl9iYXNlIHsgfTsKY2xhc3MgQ19za2VsIDogdmlydHVhbCBwdWJsaWMgQ19iYXNlLCB2aXJ0
dWFsIHB1YmxpYyBCX3NrZWwgeyB9OwoKY2xhc3MgRF9iYXNlIDogdmlydHVhbCBwdWJsaWMgQ19i
YXNlIHsgfTsKY2xhc3MgRF9za2VsIDogdmlydHVhbCBwdWJsaWMgRF9iYXNlLCB2aXJ0dWFsIHB1
YmxpYyBDX3NrZWwgeyB9OwoKY2xhc3MgRF9pbXBsIDogdmlydHVhbCBwdWJsaWMgRF9za2VsIHsg
fTsKCmludCBtYWluKCkKewoJRF9pbXBsIGk7Cn0K


             reply	other threads:[~2001-06-05 15:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-05 15:46 Franz.Sirl-kernel [this message]
2001-06-08  7:31 nathan

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=20010605224419.4977.qmail@sourceware.cygnus.com \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=stefan@space.twc.de \
    /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).