From: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
To: Florian Weimer <fweimer@redhat.com>, Steve Ellcey <sellcey@marvell.com>
Cc: nd <nd@arm.com>, "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [RFC PATCH 1/2] Aarch64: Add simd exp/expf ABI symbols
Date: Mon, 15 Jul 2019 11:04:01 +0000 [thread overview]
Message-ID: <08ac957c-2dfa-dd9c-83c1-69224ef12056@arm.com> (raw)
In-Reply-To: <874l3nva69.fsf@oldenburg2.str.redhat.com>
On 15/07/2019 11:55, Florian Weimer wrote:
> * Steve Ellcey:
>
>> I think it is necessary to have some object (even if it is not used)
>> that is put in the libmvec-static-only-routines list of objects in
>> sysdeps/aarch64/fpu/Makefile in order to build libmvec_nonshared.a. If
>> you don't have that library the linker script fails when it cannot find
>> it.
>
> Maybe you could make the generation of the linker script optional in
> math/Makefile?
the linker script is needed anyway to add libmvec.so,
just the libmvec_nonshared.a part can be dropped on
targets that don't need it.
but it's easier to have an empty libmvec_nonshared.a
(it would be nicer if all symbols were in libm.so
without any linker script and nonshared hack, but
i guess it's too late for that)
prev parent reply other threads:[~2019-07-15 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 11:09 [RFC PATCH 1/2] Aarch64: Add simd exp/expf ABI symbols Szabolcs Nagy
2019-07-08 18:00 ` Tulio Magno Quites Machado Filho
2019-07-09 8:52 ` Szabolcs Nagy
2019-07-09 10:00 ` Florian Weimer
2019-07-12 21:51 ` Steve Ellcey
2019-07-15 10:33 ` Szabolcs Nagy
2019-07-15 17:14 ` [EXT] " Steve Ellcey
2019-07-15 18:28 ` Szabolcs Nagy
2019-07-15 17:25 ` Andreas Schwab
2019-07-15 18:29 ` Szabolcs Nagy
2019-07-15 10:55 ` Florian Weimer
2019-07-15 11:04 ` Szabolcs Nagy [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=08ac957c-2dfa-dd9c-83c1-69224ef12056@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=sellcey@marvell.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).