From: Akhilesh Chirlancha <akhileshchirlancha.linux@gmail.com>
To: iant@google.com
Cc: gcc-help@gcc.gnu.org
Subject: input sections difference "ax" vs "axG" ?
Date: Tue, 1 Sep 2020 21:41:17 +0530 [thread overview]
Message-ID: <CAHJJy=U3CNbm6_fvaN=98N-i-RmuKuDwezUdFBfz9-vHAeYbCQ@mail.gmail.com> (raw)
Why the same ARM gcc creating 2 different types of input sections?
(.gnu.linkonce.t "ax") and (.group "axG")
I have 2 ARM toolchain releases. one toolchain is generating the input
sections with ".gnu.linkonce.t" prefix('ax') and another toolchain is with
".group" sections('axG').
And the toolchain with the .gnu.linkonce.t is throwing an error sometimes
""defined in discarded section" and "undefined reference"".
I do not have any clue why it's choosing 2 different types of input
sections even if there are no changes in the toolchain sources.
What could be the reason behind this? If there is somewhere better for me
to be looking, I would appreciate a pointer.
FYI, my toolchain components versions are gcc-5.2.0, binutils-2.25.1,
glibc-2.22
<----------------------------------------------------------------------------------------------------------------------------------------------->
toolchain-1:
=========
.file "sample.cpp"
.section .gnu.linkonce.t._ZN6SampleC1Ev,"ax",%progbits
.align 2
.weak _ZN6SampleC1Ev
.section
.gnu.linkonce.t._ZN6Sample10inline_funEv,"ax",%progbits
.align 2
.weak _ZN6Sample10inline_funEv
toolchain-2:
=========
.file "sample.cpp"
.section
.text._ZN6SampleC2Ev,"axG",%progbits,_ZN6SampleC5Ev,comdat
.align 2
.weak _ZN6SampleC2Ev
.section
.text._ZN6Sample10inline_funEv,"axG",%progbits,_ZN6Sample10inline_funEv,comdat
.align 2
.weak _ZN6Sample10inline_funEv
<----------------------------------------------------------------------------------------------------------------------------------------------->
-Akhilesh
next reply other threads:[~2020-09-01 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 16:11 Akhilesh Chirlancha [this message]
2020-09-01 17:20 ` Ian Lance Taylor
2020-09-02 8:03 ` Akhilesh Chirlancha
2020-09-02 19:57 ` Ian Lance Taylor
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='CAHJJy=U3CNbm6_fvaN=98N-i-RmuKuDwezUdFBfz9-vHAeYbCQ@mail.gmail.com' \
--to=akhileshchirlancha.linux@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
/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).