From: Xi Ruoyao <xry111@xry111.site>
To: binutils@sourceware.org
Cc: Pierre Labastie <pierre.labastie@neuf.fr>
Subject: question: i386 ld.gold reports "internal error" linking files with SHT_RELA section
Date: Tue, 30 Aug 2022 22:38:42 +0800 [thread overview]
Message-ID: <199ec63c39a4a323e93402277c1cc67f5c8216bf.camel@xry111.site> (raw)
Building SeaMonkey on i686 results:
"/usr/bin/ld.gold: internal error in relocate_section, at ../../gold/i386.cc:3683"
i386.cc:3683 is:
gold_assert(sh_type == elfcpp::SHT_REL);
AFAIK i386 normally use SHT_REL and x86_64 normally use SHT_RELA. But
we've found that nasm-2.15.05 generates SHT_RELA for i386 as well.
So should SHT_RELA be allowed for i386 at all? If "yes" we should fix
it for gold, if "no" we should fix it for nasm.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next reply other threads:[~2022-08-30 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 14:38 Xi Ruoyao [this message]
2022-08-30 18:21 ` H.J. Lu
2022-08-30 18:53 ` Pierre Labastie
2022-08-30 20:36 ` H.J. Lu
2022-08-31 4:43 ` Xi Ruoyao
2022-08-31 19:20 ` H.J. Lu
2022-09-01 0:47 ` Xi Ruoyao
2022-09-01 16:34 ` H.J. Lu
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=199ec63c39a4a323e93402277c1cc67f5c8216bf.camel@xry111.site \
--to=xry111@xry111.site \
--cc=binutils@sourceware.org \
--cc=pierre.labastie@neuf.fr \
/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).