public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek 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: Tue, 16 Nov 2021 22:24:45 +0000 [thread overview]
Message-ID: <bug-103291-4-hw0e1iisyO@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
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> Most likely introduced by the same commit too (r11-3699-g4e62aca0e0).
Yes. r11-3698:
_Z12hidden_fetchv:
.LFB0:
pushq %rbp
.LCFI0:
movq %rsp, %rbp
.LCFI1:
movl hidden_global(%rip), %eax
popq %rbp
.LCFI2:
ret
r11-3699:
_Z12hidden_fetchv:
.LFB0:
pushq %rbp
.LCFI0:
movq %rsp, %rbp
.LCFI1:
movq hidden_global@GOTPCREL(%rip), %rax
movl (%rax), %eax
popq %rbp
.LCFI2:
ret
next prev parent reply other threads:[~2021-11-16 22:24 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 [this message]
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
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-hw0e1iisyO@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).