public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/22575] New: immutable object placed in .bss section. Date: Wed, 20 Jul 2005 18:45:00 -0000 [thread overview] Message-ID: <20050720184103.22575.pluto@agmk.net> (raw) class obj { private: int value; private: obj() { } obj(int v) : value(v) { } public: int getValue() const { return value; } const static obj seven; }; const obj obj::seven = obj(7); int getSeven() { return obj::seven.getValue(); } gcc (3.3.6,4.1.0) places this immutable const static object in .bss section and calls constructor(int) in .ctors section. why it isn't placed in .rodata ? -- Summary: immutable object placed in .bss section. Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pluto at agmk dot net CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pld-linux GCC host triplet: i686-pld-linux GCC target triplet: i686-pld-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22575
next reply other threads:[~2005-07-20 18:41 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-20 18:45 pluto at agmk dot net [this message] 2005-07-20 18:45 ` [Bug c++/22575] " pinskia at gcc dot gnu dot org 2005-07-20 18:58 ` schlie at comcast dot net 2005-07-20 19:47 ` bangerth at dealii dot org 2005-07-20 19:49 ` bangerth at dealii dot org 2005-07-20 19:50 ` bangerth at dealii dot org 2005-07-20 20:03 ` pinskia at gcc dot gnu dot org 2005-07-21 2:35 ` giovannibajo at libero dot it 2005-07-21 23:11 ` bangerth at dealii dot 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=20050720184103.22575.pluto@agmk.net \ --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: linkBe 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).