public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93369] [10 regression] g++.dg/lto/pr64076 fails
Date: Thu, 09 Apr 2020 11:59:01 +0000 [thread overview]
Message-ID: <bug-93369-4-Xk3YntBZSB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93369-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93369
--- Comment #20 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:bb40460646ce4e6ad27a2f6795106d004d405314
commit r10-7652-gbb40460646ce4e6ad27a2f6795106d004d405314
Author: Richard Biener <rguenther@suse.de>
Date: Thu Apr 9 13:54:01 2020 +0200
testsuite/93369 - use -shared to avoid issue with ODR violation
The testcase contains an ODR violation and thus the observed
link failure is an accepted outcome (it originally was for
an ICE during WPA). Thus the following adds -shared to the link.
2020-04-09 Richard Biener <rguenther@suse.de>
PR testsuite/93369
* g++.dg/lto/pr64076_0.C: Add -shared -fPIC.
* g++.dg/lto/pr64076_1.C: Add -fPIC.
next prev parent reply other threads:[~2020-04-09 11:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93369-4@http.gcc.gnu.org/bugzilla/>
2020-03-19 21:44 ` hubicka at gcc dot gnu.org
2020-03-26 12:07 ` marxin at gcc dot gnu.org
2020-04-04 10:11 ` hubicka at gcc dot gnu.org
2020-04-09 8:47 ` rguenth at gcc dot gnu.org
2020-04-09 11:28 ` hubicka at gcc dot gnu.org
2020-04-09 11:59 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-09 11:59 ` rguenth 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-93369-4-Xk3YntBZSB@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).