public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: Nelson Chu <nelson.chu@sifive.com>
Cc: jiawei <jiawei@iscas.ac.cn>, Binutils <binutils@sourceware.org>,
	"Kito Cheng" <kito.cheng@sifive.com>,
	"Jim Wilson" <jim.wilson.gcc@gmail.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	cmuellner@ventanamicro.com,
	"Philipp Tomsich" <philipp.tomsich@vrull.eu>,
	"Wei Wu (吴伟)" <lazyparser@gmail.com>,
	sinan@isrc.iscas.ac.cn, shihua@iscas.ac.cn,
	yulong@nj.iscas.ac.cn, "Nick Alcock" <nick.alcock@oracle.com>
Subject: Re: [PATCH 1/1] Fix ld error due to lto shared not support.
Date: Wed, 05 Jan 2022 17:39:06 +0000	[thread overview]
Message-ID: <87k0fegk05.fsf@esperi.org.uk> (raw)
In-Reply-To: <CAJYME4GshbSSzQxsQkbc=zJazjccmMDrSmK0qECJJ+JXcZmNGQ@mail.gmail.com> (Nelson Chu's message of "Wed, 22 Dec 2021 20:20:39 +0800")

On 22 Dec 2021, Nelson Chu verbalised:
> Added Nick Alcock in the cc list :)

Thanks!

> On Tue, Dec 21, 2021 at 5:29 PM jiawei <jiawei@iscas.ac.cn> wrote:
> I notice that there are 41 ld-ctf testcases, and all of them need
> -shared option, so we probably can just add the following check in the
> ctf.exp,
>
> if ![check_shared_lib_support]  {
>     return 0
> }
>
> So that we don't run these testcases when the ld doesn't support the
> -shared option, and you don't need to modify the whole 41 testcases.

Sure!

Many of them (but not all) would be just as happy with -Wl,-Bdynamic,
but that seems likely to be less widely available than -shared...

>>  ld/testsuite/ld-plugin/lto.exp                               | 2 +-
>>  42 files changed, 43 insertions(+), 2 deletions(-)
>> diff --git a/ld/testsuite/ld-ctf/array.d b/ld/testsuite/ld-ctf/array.d
>> index 0fe675e2c5d..7a02de49ef9 100644
>> --- a/ld/testsuite/ld-ctf/array.d
>> +++ b/ld/testsuite/ld-ctf/array.d
>> @@ -2,8 +2,9 @@
>>  #source: array-char.c
>>  #source: array-int.c
>>  #objdump: --ctf
>> -#ld: -shared --ctf-variables --hash-style=sysv
>> +#ld: --ctf-variables --hash-style=sysv

... did you mean to do this?

(A bunch of tests in the libctf testsuite may need similar changes.)

-- 
NULL && (void)

  reply	other threads:[~2022-01-05 17:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21  9:28 [PATCH 0/1] " jiawei
2021-12-21  9:28 ` [PATCH 1/1] " jiawei
2021-12-22 12:20   ` Nelson Chu
2022-01-05 17:39     ` Nick Alcock [this message]
2022-01-06  2:45       ` Nelson Chu

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=87k0fegk05.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.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=nelson.chu@sifive.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).