From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: <kai.kang@windriver.com>, <libc-alpha@sourceware.org>
Subject: Re: [RFC PATCH] math-vector-fortran.h: fix multilib conflict
Date: Mon, 29 Apr 2024 15:09:02 +0100 [thread overview]
Message-ID: <Zi+p/oIM1WUWKg0I@arm.com> (raw)
In-Reply-To: <20240417033559.1372027-1-kai.kang@windriver.com>
The 04/17/2024 11:35, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> The header files math-vector-fortran.h fail to install with confliction
> when multilib enabled. Update sysdeps/aarch64/fpu/finclude/math-vector-fortran.h
> to only valid for aarch64. And create a link for arm to fix the
> confliction.
what kind of multilib are you talking about?
aarch64 and armhf on the same system?
i think those cannot share header files on the same system.
> +!GCC$ builtin (acos) attributes simd (notinbranch) if('aarch64')
note this would disable the simd attribute on aarch64_be
(which is technically supported by glibc)
prev parent reply other threads:[~2024-04-29 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 3:35 kai.kang
2024-04-29 13:45 ` Florian Weimer
2024-04-29 14:09 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zi+p/oIM1WUWKg0I@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=kai.kang@windriver.com \
--cc=libc-alpha@sourceware.org \
/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).