public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: porten@trolltech.com To: gcc-gnats@gcc.gnu.org Subject: other/4878: gcc 3.0.2 output crashes HP-UX linker Date: Fri, 02 Nov 2001 14:40:00 -0000 [thread overview] Message-ID: <20011114185532.3074.qmail@sourceware.cygnus.com> (raw) >Number: 4878 >Category: other >Synopsis: gcc 3.0.2 output crashes HP-UX linker >Confidential: no >Severity: serious >Priority: high >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Wed Nov 14 10:56:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Harri Porten >Release: gcc version 3.0.2 >Organization: >Environment: hppa1.1-hp-hpux10.20 (and 11.00) /usr/bin/ld B.10.37 991028 bintuils 2.11.2 >Description: The following piece of code will crash HP's system linker (B.10.37) when trying to build a shared library: struct X { virtual ~X(); }; struct Y { virtual void foo(); }; struct W : public X, public Y { virtual void foo(); }; struct Q : public W { }; void bar() { Q q; } I know it mustn't be gcc's fault as /usr/bin/ld is at least partly guilty because of it's fatal reaction. But where is the real problem ? >How-To-Repeat: g++ -shared -fPIC crash.cpp >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-11-14 18:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-11-02 14:40 porten [this message] 2002-01-04 21:46 rodrigc 2002-01-07 2:26 Harri Porten 2002-01-07 8:01 rodrigc 2002-02-26 18:32 rodrigc 2002-02-27 9:00 rodrigc
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=20011114185532.3074.qmail@sourceware.cygnus.com \ --to=porten@trolltech.com \ --cc=gcc-gnats@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: linkBe 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).