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 target/110709] how to handle the initialization of global struct data for position independent executable application. Date: Tue, 18 Jul 2023 04:19:10 +0000 [thread overview] Message-ID: <bug-110709-4-WbjMvXg2E5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110709-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110709 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I don't understand your question since if we look at the output of GCC we get: .LC0: .ascii "const char *text\000" .section .data.rel.local,"aw" .align 2 .type user_test, %object .size user_test, 112 user_test: .ascii "struct member testChArray\000" .space 74 .word 10 .word .LC0 .word 27 Only text will have a relocation associated with it since that is the only one that needs it. Everything else has no need for a relocation since it is just data.
next prev parent reply other threads:[~2023-07-18 4:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-18 4:09 [Bug c/110709] New: " wangwen at microsoft dot com 2023-07-18 4:19 ` pinskia at gcc dot gnu.org [this message] 2023-07-18 4:22 ` [Bug target/110709] " pinskia at gcc dot gnu.org 2023-07-18 4:39 ` wangwen at microsoft dot com 2023-07-18 5:00 ` pinskia at gcc dot gnu.org 2023-07-18 7:01 ` xry111 at gcc dot gnu.org 2023-07-18 13:30 ` wangwen at microsoft dot com 2023-07-18 14:05 ` xry111 at gcc dot gnu.org 2023-07-18 14:41 ` wangwen at microsoft dot com
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-110709-4-WbjMvXg2E5@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).