From: Nelson Chu <nelson.chu@sifive.com>
To: Jim Wilson <jim.wilson.gcc@gmail.com>
Cc: jiawei <jiawei@iscas.ac.cn>, Binutils <binutils@sourceware.org>,
"Kito Cheng" <kito.cheng@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
cmuellner@ventanamicro.com,
"Philipp Tomsich" <philipp.tomsich@vrull.eu>,
"Nick Alcock" <nick.alcock@oracle.com>,
"Wei Wu (吴伟)" <lazyparser@gmail.com>,
sinan@isrc.iscas.ac.cn, shihua@iscas.ac.cn,
yulong@nj.iscas.ac.cn
Subject: Re: [v2 PATCH 0/1] Fix ld error due to '-shared' not support
Date: Tue, 28 Dec 2021 12:20:58 +0800 [thread overview]
Message-ID: <CAJYME4HOV70seQjZN2s73PYwGdVtFcrO2VrVX74JTOpVO5Mn6A@mail.gmail.com> (raw)
In-Reply-To: <CALNwTfyG+-ns1aR_=QCG8EGLSnETb_bx2VWf-2O=cBUNpGnnRQ@mail.gmail.com>
On Tue, Dec 28, 2021 at 7:07 AM Jim Wilson <jim.wilson.gcc@gmail.com> wrote:
>
> On Wed, Dec 22, 2021 at 10:20 PM jiawei <jiawei@iscas.ac.cn> wrote:
>>
>> jiawei (1):
>> Fix ld error due to -shared not support.
>>
>> ld/testsuite/ld-ctf/ctf.exp | 5 +++++
>> ld/testsuite/ld-plugin/lto.exp | 2 +-
>> 2 files changed, 6 insertions(+), 1 deletion(-)
>
>
> This looks OK to me. I don't think --shared is required by the ctf support, maybe adding that just made the tests easier to write. Meanwhile, since they all use --shared it is OK to add the check to verify that --shared is supported. And the lto.exp change is trivially correct also.
Thanks, committed.
> Another way to fix this is to add the missing newlib support we need to make riscv*-elf shared library support work, and then we can enable the linker shared library support for riscv*-elf. The linker support is fine. it is just that all --shared tests will fail because of the newlib problem, which then leads to confusing ld testsuite results. But fixing newlib is more of a long term issue, and in the short term we should fix the ld testsuite.
Yeah, I remember we have similar pr in the sourceware that need to
support riscv shared newlib.
https://sourceware.org/bugzilla/show_bug.cgi?id=25527
Thanks
Nelson
>
prev parent reply other threads:[~2021-12-28 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 6:19 jiawei
2021-12-23 6:19 ` [v2 PATCH 1/1] Fix ld error due to -shared " jiawei
2021-12-27 23:07 ` [v2 PATCH 0/1] Fix ld error due to '-shared' " Jim Wilson
2021-12-28 4:20 ` Nelson Chu [this message]
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=CAJYME4HOV70seQjZN2s73PYwGdVtFcrO2VrVX74JTOpVO5Mn6A@mail.gmail.com \
--to=nelson.chu@sifive.com \
--cc=binutils@sourceware.org \
--cc=cmuellner@ventanamicro.com \
--cc=jiawei@iscas.ac.cn \
--cc=jim.wilson.gcc@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=lazyparser@gmail.com \
--cc=nick.alcock@oracle.com \
--cc=palmer@dabbelt.com \
--cc=philipp.tomsich@vrull.eu \
--cc=shihua@iscas.ac.cn \
--cc=sinan@isrc.iscas.ac.cn \
--cc=yulong@nj.iscas.ac.cn \
/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).