public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113976] [11/12/13/14 Regression] explicit instantiation of const variable template following implicit instantiation is assembled in .rodata instead of .bss since r8-2857-g2ec399d8a6c9c2
Date: Sun, 18 Feb 2024 18:09:32 +0000 [thread overview]
Message-ID: <bug-113976-4-5LPPZAfxxd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113976-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113976
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #3)
> What does the standard say about changing const objects?
It says it is undefined. Note there is no changing const object in this code;
just the const variable is dynamically initialized which is 100% defined.
next prev parent reply other threads:[~2024-02-18 18:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 21:17 [Bug c++/113976] New: explicit instantiation of const variable template following implicit instantiation is assembled in .rodata instead of .bss tamiko at gentoo dot org
2024-02-17 21:29 ` [Bug c++/113976] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2024-02-18 6:49 ` sjames at gcc dot gnu.org
2024-02-18 8:03 ` tamiko at gentoo dot org
2024-02-18 18:06 ` [Bug c++/113976] [11/12/13/14 Regression] explicit instantiation of const variable template following implicit instantiation is assembled in .rodata instead of .bss since r8-2857-g2ec399d8a6c9c2 law at gcc dot gnu.org
2024-02-18 18:09 ` pinskia at gcc dot gnu.org [this message]
2024-02-18 18:39 ` jakub at gcc dot gnu.org
2024-02-19 8:10 ` rguenth at gcc dot gnu.org
2024-02-19 16:00 ` jakub at gcc dot gnu.org
2024-02-19 16:58 ` jakub at gcc dot gnu.org
2024-02-19 17:30 ` jakub at gcc dot gnu.org
2024-02-19 17:49 ` jakub at gcc dot gnu.org
2024-02-19 18:15 ` ppalka at gcc dot gnu.org
2024-02-28 22:22 ` cvs-commit at gcc dot gnu.org
2024-03-01 14:38 ` [Bug c++/113976] [11/12/13 " jakub 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-113976-4-5LPPZAfxxd@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).