From: mengqinggang <mengqinggang@loongson.cn>
To: Peng Fan <fanpeng@loongson.cn>, binutils@sourceware.org
Cc: cailulu@loongson.cn, xry111@xry111.site
Subject: Re: [PATCH] LoongArch: Modify inconsistent behavior of ld with --unresolved-symbols=ignore-all
Date: Thu, 22 Feb 2024 17:12:38 +0800 [thread overview]
Message-ID: <4a080f22-f610-9acb-0ecf-1b94a207419c@loongson.cn> (raw)
In-Reply-To: <20240220061459.3353898-1-fanpeng@loongson.cn>
在 2024/2/20 下午2:14, Peng Fan 写道:
> Ignore errors when producing executable files that reference external symbols defined
> in other files.
>
> Testcase is:
> resolv.c:
> int main(int argc, char *argv[]) {
> return argc;
> }
>
> t.c:
>
> extern const struct my_struct ms1;
> static const struct my_struct *ms = &ms1;
>
> t.h:
> typedef struct my_struct {
> char *str;
> int i;
> } my_struct;
>
> Compiling and linking command with:
> gcc t.c -c ; gcc resolv.c -c
> gcc resolv.o t.o -o resolv -Wl,--unresolved-symbols=ignore-all
>
> Got error as:
> ~/install/usr/bin/ld: t.o:(.data.rel+0x0): undefined reference to `ms1'
> collect2: error: ld returned 1 exit status
>
> ---
> bfd/elfnn-loongarch.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/bfd/elfnn-loongarch.c b/bfd/elfnn-loongarch.c
> index 1895699af06..6b2d5a7164d 100644
> --- a/bfd/elfnn-loongarch.c
> +++ b/bfd/elfnn-loongarch.c
> @@ -2662,6 +2662,7 @@ loongarch_elf_relocate_section (bfd *output_bfd, struct bfd_link_info *info,
> char tls_type;
> bfd_vma relocation, off, ie_off, desc_off;
> int i, j;
> + bool ignored = false;
>
> howto = loongarch_elf_rtype_to_howto (input_bfd, r_type);
> if (howto == NULL || r_type == R_LARCH_GNU_VTINHERIT
> @@ -2703,7 +2704,7 @@ loongarch_elf_relocate_section (bfd *output_bfd, struct bfd_link_info *info,
> }
> else
> {
> - bool warned, ignored;
> + bool warned;
>
> RELOC_FOR_GLOBAL_SYMBOL (info, input_bfd, input_section, rel,
> r_symndx, symtab_hdr, sym_hashes,
> @@ -2867,7 +2868,7 @@ loongarch_elf_relocate_section (bfd *output_bfd, struct bfd_link_info *info,
> {
> if (h->dynindx == -1)
> {
> - if (h->root.type == bfd_link_hash_undefined)
> + if (h->root.type == bfd_link_hash_undefined && !ignored)
RELOC_FOR_GLOBAL_SYMBOL macro also check undefined symbol, this check can delete directly.
> (*info->callbacks->undefined_symbol)
> (info, name, input_bfd, input_section,
> rel->r_offset, true);
next prev parent reply other threads:[~2024-02-22 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 6:14 Peng Fan
2024-02-22 9:12 ` mengqinggang [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-20 2:11 ticat-fp
2024-02-20 2:31 ` Xi Ruoyao
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=4a080f22-f610-9acb-0ecf-1b94a207419c@loongson.cn \
--to=mengqinggang@loongson.cn \
--cc=binutils@sourceware.org \
--cc=cailulu@loongson.cn \
--cc=fanpeng@loongson.cn \
--cc=xry111@xry111.site \
/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).