From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, testsuite]: Fix PR 65944, FAIL: g++.dg/lto/pr65276: undefined reference to std2::exception::~exception()
Date: Wed, 17 Jun 2015 10:17:00 -0000 [thread overview]
Message-ID: <CAFULd4bKjgBGOpVx3y7g1-3RpaxpjmSh7-Ak2HzeM=XiQmQKxQ@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4b0-H_XFkGHBHR5LdTRjtLH_+C1=k2H+FwpiLg0=K2-kw@mail.gmail.com>
On Tue, Jun 16, 2015 at 5:13 PM, Uros Bizjak <ubizjak@gmail.com> wrote:
> Hello!
>
> Following patch fixes:
>
> cp_lto_pr65276_1.o: In function `std2::runtime_error::~runtime_error()':^M
> pr65276_1.C:(.text._ZN4std213runtime_errorD2Ev[_ZN4std213runtime_errorD5Ev]+0x8):
> undefined reference to `std2::exception::~exception()'^M
> cp_lto_pr65276_1.o: In function `std2::runtime_error::~runtime_error()':^M
> pr65276_1.C:(.text._ZN4std213runtime_errorD0Ev[_ZN4std213runtime_errorD5Ev]+0xc):
> undefined reference to `std2::exception::~exception()'^M
> cp_lto_pr65276_1.o:(.rodata._ZTVN4std29exceptionE[_ZTVN4std29exceptionE]+0x10):
> undefined reference to `std2::exception::~exception()'^M
> cp_lto_pr65276_1.o:(.rodata._ZTVN4std29exceptionE[_ZTVN4std29exceptionE]+0x18):
> undefined reference to `std2::exception::~exception()'^M
> collect2: error: ld returned 1 exit status^M
>
> link error with g++.dg/lto/pr65276 testcase.
>
> 2015-06-16 Uros Bizjak <ubizjak@gmail.com>
>
> PR testsuite/65944
> * g++.dg/lto/pr65276_0.C: Add std2::exception::~exception() function.
>
> Tested on x86_64-linux-gnu CentOS 5.11 (where linking failed) and
> Fedora 22 (where linking didn't fail).
>
> OK for mainline and gcc-5 branch?
Now committed as obvious.
Uros.
next prev parent reply other threads:[~2015-06-17 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 15:32 Uros Bizjak
2015-06-17 10:17 ` Uros Bizjak [this message]
2015-06-18 9:05 ` James Greenhalgh
2015-06-18 9:32 ` Uros Bizjak
2015-06-18 9:43 ` Uros Bizjak
2016-02-02 3:09 ` Michael Daniels
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='CAFULd4bKjgBGOpVx3y7g1-3RpaxpjmSh7-Ak2HzeM=XiQmQKxQ@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@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).