From: "luizluca at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug backends/25832] New: aarch64 fails to compile with musl
Date: Thu, 16 Apr 2020 06:34:14 +0000 [thread overview]
Message-ID: <bug-25832-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25832
Bug ID: 25832
Summary: aarch64 fails to compile with musl
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: backends
Assignee: unassigned at sourceware dot org
Reporter: luizluca at gmail dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Hello
gibc has user_fpsimd_struct.vregs as __uint128_t
https://github.com/bminor/glibc/blob/master/sysdeps/unix/sysv/linux/aarch64/sys/user.h#L32
while musl has it as long double:
https://github.com/AssemblyScript/musl/blob/master/arch/aarch64/bits/user.h#L9
While building 0.179 with musl, I got this error:
aarch64_initreg.c: In function 'aarch64_set_initial_registers_tid':
aarch64_initreg.c:85:37: error: invalid operands to binary & (have 'long
double' and 'unsigned int')
dwarf_fregs[r] = fregs.vregs[r] & 0xFFFFFFFF;
~~~~~~~~~~~~~~ ^
make[6]: *** [Makefile:682: aarch64_initreg.o] Error 1
make[5]: *** [Makefile:499: all-recursive] Error 1
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-04-16 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 6:34 luizluca at gmail dot com [this message]
2020-04-16 14:00 ` [Bug backends/25832] " mark at klomp dot org
2020-05-13 17:09 ` anarchy at gentoo dot org
2020-06-19 10:05 ` mark at klomp dot org
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=bug-25832-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).