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 c++/94426] [10 Regression] ICE in mangle_decl with -flto
Date: Thu, 16 Apr 2020 20:15:01 +0000 [thread overview]
Message-ID: <bug-94426-4-n5uVgWMUxA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94426-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94426
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>:
https://gcc.gnu.org/g:b084efe3fcdfcf88e1703800b9b99347e89beefb
commit r10-7761-gb084efe3fcdfcf88e1703800b9b99347e89beefb
Author: Iain Sandoe <iain@sandoe.co.uk>
Date: Thu Apr 16 21:13:51 2020 +0100
testsuite: Update pr94426-2 test to handle more targets [PR94426]
The function (_Z4InitIN3VARIZ1qvEUlvE_EUlvE_EEbT_) that initializes
VAR has changed siganture. It was was weak / comdat [Linux] or
weak / global [Darwin] and now is text section local.
So: test that the symbol exists, is spelled the way intended by the
ABI mangling and is not weak (or global on Darwin).
gcc/testsuite/ChangeLog:
2020-04-16 Iain Sandoe <iain@sandoe.co.uk>
PR c++/94426
* g++.dg/cpp0x/lambda/pr94426-2.C: Adjust scan-asms to test
for the change on more platforms.
prev parent reply other threads:[~2020-04-16 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 15:25 [Bug c++/94426] New: " jakub at gcc dot gnu.org
2020-03-31 15:25 ` [Bug c++/94426] " jakub at gcc dot gnu.org
2020-04-01 7:00 ` rguenth at gcc dot gnu.org
2020-04-01 8:33 ` jakub at gcc dot gnu.org
2020-04-01 11:00 ` jakub at gcc dot gnu.org
2020-04-01 12:34 ` nathan at gcc dot gnu.org
2020-04-01 12:44 ` jakub at gcc dot gnu.org
2020-04-01 13:14 ` nathan at gcc dot gnu.org
2020-04-01 17:41 ` nathan at gcc dot gnu.org
2020-04-13 13:39 ` nathan at gcc dot gnu.org
2020-04-16 20:15 ` cvs-commit at gcc dot gnu.org [this message]
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-94426-4-n5uVgWMUxA@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).