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++/103291] [11/12 Regression] #pragma gcc visibility is lost for external decls declared inside a function
Date: Mon, 28 Mar 2022 13:37:39 +0000 [thread overview]
Message-ID: <bug-103291-4-833r56CKXI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103291-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103291
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:
https://gcc.gnu.org/g:8796eb27e24bd3340ebd393e96a94b91d09407e9
commit r12-7854-g8796eb27e24bd3340ebd393e96a94b91d09407e9
Author: Jason Merrill <jason@redhat.com>
Date: Sun Mar 27 09:44:59 2022 -0400
c++: visibility of local extern [PR103291]
When setting up the hidden namespace-scope decl for a local extern, we also
need to set its visibility.
PR c++/103291
gcc/cp/ChangeLog:
* name-lookup.cc (push_local_extern_decl_alias): Call
determine_visibility.
gcc/testsuite/ChangeLog:
* g++.dg/ext/visibility/visibility-local-extern1.C: New test.
next prev parent reply other threads:[~2022-03-28 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 22:01 [Bug c++/103291] New: gcc 11 regression with #pragma GCC visibility vs extern inside C++ functions roland at gnu dot org
2021-11-16 22:13 ` [Bug c++/103291] [11/12 Regression] visibility is lost for external decls declared inside a function pinskia at gcc dot gnu.org
2021-11-16 22:15 ` pinskia at gcc dot gnu.org
2021-11-16 22:19 ` [Bug c++/103291] [11/12 Regression] #pragma gcc " pinskia at gcc dot gnu.org
2021-11-16 22:24 ` mpolacek at gcc dot gnu.org
2021-11-18 7:41 ` rguenth at gcc dot gnu.org
2021-11-18 9:46 ` jakub at gcc dot gnu.org
2022-03-27 13:38 ` jason at gcc dot gnu.org
2022-03-28 13:37 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-28 19:12 ` [Bug c++/103291] [11 " cvs-commit at gcc dot gnu.org
2022-03-28 19:19 ` jason 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-103291-4-833r56CKXI@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).