From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Subject: Is aarch64_be-linux-gnu_ilp32 supported?
Date: Thu, 20 Apr 2023 09:03:31 +0930 [thread overview]
Message-ID: <ZEB6S9DBGiRh+3vJ@squeak.grove.modra.org> (raw)
I added aarch64_be-linux-gnu_ilp32 a while ago to my list of targets
to test before pushing global changes, but I'm thinking I ought to drop
it. The ld testsuite gets segmentation faults, and the list of fails
is quite large. No doubt it would be worse if I had installed a
cross-compiler for the target.
aarch64_be-linux-gnu_ilp32 FAIL: binutils-all/aarch64/sve-dwarf-registers
aarch64_be-linux-gnu_ilp32 FAIL: Disassembler detects unallocated instruction encodings.
aarch64_be-linux-gnu_ilp32 FAIL: binutils-all/strip-14
aarch64_be-linux-gnu_ilp32 FAIL: binutils-all/strip-15
aarch64_be-linux-gnu_ilp32 FAIL: gas/aarch64/reloc-prel_g1_nc
aarch64_be-linux-gnu_ilp32 FAIL: gas/aarch64/reloc-prel_g2
aarch64_be-linux-gnu_ilp32 FAIL: gas/aarch64/reloc-prel_g2_nc
aarch64_be-linux-gnu_ilp32 FAIL: gas/aarch64/reloc-prel_g3
aarch64_be-linux-gnu_ilp32 FAIL: gas/aarch64/symbol-variant_pcs-1
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/erratum843419_tls_ie
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/erratum843419-far-adr
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/erratum843419-far-full
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/emit-relocs-257-be
aarch64_be-linux-gnu_ilp32 FAIL: aarch64-farcall-b-gsym
aarch64_be-linux-gnu_ilp32 FAIL: aarch64-farcall-group
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-all
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-gd-le
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-gdesc-le
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-gdesc-le-now
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-ie-le
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-ld-le-small
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-ld-le-tiny
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-desc-ie
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-gdesc-le-2
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-ie-le-2
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-ie-le-3
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-tiny-gd
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-tiny-gd-le
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-tiny-desc
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-tiny-desc-le
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-tiny-ie
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-tiny-ld
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-small-ld
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tlsle-symbol-offset
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/gc-got-relocs
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/gc-tls-relocs
aarch64_be-linux-gnu_ilp32 FAIL: TLS offset out of range
aarch64_be-linux-gnu_ilp32 FAIL: TLS offset out of range - TPREL_ADD_LO12
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/protected-data
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-gd-ie
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-large-gd-ie-be
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-large-desc-ie-be
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-gdesc-ie
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-gdesc-ie-2
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-tiny-gd-ie
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-tiny-desc-ie
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-gd-ie-2
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-gd-ie-3
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/tls-relax-ie-le-4
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/relasz
aarch64_be-linux-gnu_ilp32 FAIL: AArch64 mapping symbol for plt section test.
aarch64_be-linux-gnu_ilp32 FAIL: GNU Property (single input, combine section)
aarch64_be-linux-gnu_ilp32 FAIL: GNU Property (combine multiple with BTI)
aarch64_be-linux-gnu_ilp32 FAIL: GNU Property (combine multiple with PAC)
aarch64_be-linux-gnu_ilp32 FAIL: PT_GNU_PROPERTY alignment
aarch64_be-linux-gnu_ilp32 FAIL: Check -z force-bti emits BTI PLT (shared)
aarch64_be-linux-gnu_ilp32 FAIL: Check -z force-bti emits BTI feature (shared)
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/exe with copy relocation
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/exe with copy relocation 2
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/exe with copy relocation elimination
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/func sym hash opt for exe
aarch64_be-linux-gnu_ilp32 FAIL: Build bti-plt-so for PLT tests
aarch64_be-linux-gnu_ilp32 FAIL: Check -z force-bti emits BTI PLT (exec)
aarch64_be-linux-gnu_ilp32 FAIL: Check -z force-bti emits BTI feature (exec)
aarch64_be-linux-gnu_ilp32 FAIL: BTI PLT with only GNU PROP
aarch64_be-linux-gnu_ilp32 FAIL: Warn with one missing GNU NOTE BTI input
aarch64_be-linux-gnu_ilp32 FAIL: Warn when neither inputs has GNU NOTE BTI
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/pac-plt-1
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/pac-plt-2
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/bti-pac-plt-1
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/bti-pac-plt-2
aarch64_be-linux-gnu_ilp32 FAIL: Warn when both have GNU prop but neither BTI
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/weak-tls
aarch64_be-linux-gnu_ilp32 FAIL: ld-aarch64/undef-tls
aarch64_be-linux-gnu_ilp32 FAIL: Check linker stubs with indirect calls handle BTI (shared lib).
aarch64_be-linux-gnu_ilp32 FAIL: Check linker stubs with indirect calls handle BTI (exe).
aarch64_be-linux-gnu_ilp32 FAIL: Check linker stubs with indirect calls handle BTI when target has BTI.
--
Alan Modra
Australia Development Lab, IBM
next reply other threads:[~2023-04-19 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 23:33 Alan Modra [this message]
2023-04-19 23:41 ` Andrew Pinski
2023-04-20 0:14 ` Alan Modra
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=ZEB6S9DBGiRh+3vJ@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@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).