public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/4135: Unable to link: "non-virtual thunk" in HPUX11 and AIX (gcc-3.0.1) Date: Wed, 12 Dec 2001 08:46:00 -0000 [thread overview] Message-ID: <20011212164605.21094.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/4135; it has been noted by GNATS. From: rodrigc@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rodrigc@gcc.gnu.org, torbjorn.gard@streamserve.com Cc: Subject: Re: c++/4135: Unable to link: "non-virtual thunk" in HPUX11 and AIX (gcc-3.0.1) Date: 12 Dec 2001 16:40:02 -0000 Synopsis: Unable to link: "non-virtual thunk" in HPUX11 and AIX (gcc-3.0.1) State-Changed-From-To: open->feedback State-Changed-By: rodrigc State-Changed-When: Wed Dec 12 08:40:01 2001 State-Changed-Why: Does the patch you provided in PR 3536 solve this problem? Hello, The thunks were actually generated and found in the object files but they were not public so linking failed. Adding the three lower lines to the function make_thunk() in /gcc/cp/method.c seems solve problem 3536. Line 361: /* And neither is it a clone. */ DECL_CLONED_FUNCTION (thunk) = NULL_TREE; DECL_EXTERNAL (thunk) = 1; + /* Make the thunk public unless it is for a destructor */ + if (!DECL_DESTRUCTOR_P (func_decl)) + TREE_PUBLIC (thunk) = 1; http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4135&database=gcc
next reply other threads:[~2001-12-12 16:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-12 8:46 rodrigc [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-02-19 5:36 Craig Rodrigues 2002-02-18 23:56 N. Renuga 2002-01-27 16:58 rodrigc 2001-12-12 8:40 rodrigc 2001-08-27 2:16 torbjorn.gard
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=20011212164605.21094.qmail@sources.redhat.com \ --to=rodrigc@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).