From: Andreas Schwab <schwab@suse.de>
To: Fangrui Song via Binutils <binutils@sourceware.org>
Cc: Nelson Chu <nelson.chu@sifive.com>,
Kito Cheng <kito.cheng@sifive.com>,
Fangrui Song <maskray@google.com>
Subject: Re: [PATCH] RISC-V: Remove R_RISCV_GNU_VTINHERIT/R_RISCV_GNU_VTENTRY
Date: Mon, 08 Aug 2022 10:02:11 +0200 [thread overview]
Message-ID: <mvmtu6nkvss.fsf@suse.de> (raw)
In-Reply-To: <20220808065523.18152-1-maskray@google.com> (Fangrui Song via Binutils's message of "Sun, 7 Aug 2022 23:55:23 -0700")
On Aug 07 2022, Fangrui Song via Binutils wrote:
> There is no assembler syntax for the two relocation types and therefore
> they appear to be never used. Remove related ld code.
FWIW, they are still generically handled by the .vtable_inherit and
.vtable_entry pseudo-ops, but support for -fvtable-gc has been removed
from gcc in 2003. The RISC-V assembler never picked them up.
$ riscv64-suse-linux-as vtable.s
vtable.s: Assembler messages:
vtable.s:1: Error: cannot represent BFD_RELOC_VTABLE_ENTRY relocation in object file
vtable.s:2: Error: cannot represent BFD_RELOC_VTABLE_INHERIT relocation in object file
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2022-08-08 8:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 6:55 Fangrui Song
2022-08-08 7:36 ` Nelson Chu
2022-08-08 8:02 ` Andreas Schwab [this message]
2022-08-08 15:47 ` Kito Cheng
2022-08-08 17:27 ` Fangrui Song
2022-08-08 18:33 ` Palmer Dabbelt
2022-08-10 6:33 ` Fangrui Song
2022-08-10 13:22 ` Kito Cheng
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=mvmtu6nkvss.fsf@suse.de \
--to=schwab@suse.de \
--cc=binutils@sourceware.org \
--cc=kito.cheng@sifive.com \
--cc=maskray@google.com \
--cc=nelson.chu@sifive.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).