public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anders at kaseorg dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/37303] New: const compound initializers in structs are written to .data instead of .rodata Date: Sun, 31 Aug 2008 20:47:00 -0000 [thread overview] Message-ID: <bug-37303-7274@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1229 bytes --] GCC generates identical code for the following two structures: const struct { const int *p; } foo = { (const int []) {1, 2, 3} }; const struct { int *p; } foo = { (int []) {1, 2, 3} }; In both cases, the struct is written to the .rodata section, but the array {1, 2, 3} is written to the .data section: .section .rodata .align 8 .type foo, @object .size foo, 8 foo: .quad __compound_literal.0 .data .align 4 .type __compound_literal.0, @object .size __compound_literal.0, 12 __compound_literal.0: .long 1 .long 2 .long 3 For the first struct, where the array is const, it should also be written to the .rodata section. Im using gcc 4.3.2-0ubuntu2 on Intrepid amd64. -- Summary: const compound initializers in structs are written to .data instead of .rodata Product: gcc Version: 4.3.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: anders at kaseorg dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37303
next reply other threads:[~2008-08-31 20:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-31 20:47 anders at kaseorg dot com [this message] 2008-09-02 20:58 ` [Bug c/37303] " pinskia at gcc dot gnu dot org 2008-10-01 17:27 ` pinskia at gcc dot gnu 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=bug-37303-7274@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: 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).