From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) by sourceware.org (Postfix) with ESMTPS id D37EA3858D37 for ; Thu, 20 Apr 2023 00:14:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D37EA3858D37 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-pl1-x631.google.com with SMTP id d9443c01a7336-1a66b9bd893so5344745ad.1 for ; Wed, 19 Apr 2023 17:14:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681949660; x=1684541660; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=fGJKP1WXdrCZ5rO1n4dLiiR6qnwfqURI56uqYVrW9V4=; b=Hm/cXSzQp/BU+B6i6aZRqABEPPbdQt+5zVXdfOtKXvsOWVrEwXH3lUV6vOV39+ZUCO HWxheZ94GZ2IKxF8Ccdikc9jv5M0uEa9K59NnfPP38W2jjUfwiGDyGARgCZr7OewsDer rl5Jpn4ZlDqY9xBnR5TpH5X5opfaut1gdRI8/f92WGAq4eHb0NoMRVrtMFZ3CGdUcXjG BMjQcPKiShE2byd9zhmosHhrmRFD9aOZcMd5UUsb0KLtqqBfLxGx5Nzok5dL5qmP/E+x fNXXBtFVsprj2cnVqcrNeanWpZx/r+JGjvUXgI5UrpSPHz6d3pv98nIUpfAVR7ycQOlW i2sg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681949660; x=1684541660; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=fGJKP1WXdrCZ5rO1n4dLiiR6qnwfqURI56uqYVrW9V4=; b=Lmey1SDN9mkYO7YjwVxNmfVXbr421XNsXytOtKNdiH9NaOI+RUCwVDHYuRI+wrgfrd 9Qt0IuAxfPcV7YQd9oUt2ebg1De8hbCU2RhZkn4fYVoB364ds8RC5JTPY1j21H/y9+Ft PrTTrey+IeHx3Q+uig0xDxsJiCNDhr7Y/GfLLZ/nTkJgVSzhv3MuUGIgd3AJ/mbv0s8z yncEd/4LA5/oC6YQKgkaDRqDpyovZfXJobeq9FFNLk8e+X8KYnC10dzSTFeQTHNdgz4U PEQ4Dq4aJB5RLM5oe/lIdc58wREbJqLAimGxc7luesrMdUYTOVBdtALQh0qn9MhZu5OG 7hWA== X-Gm-Message-State: AAQBX9el9qi7Ff+wBco3lGco1ys2DoR0NdovF7wKpDL4eSYYnGbt8oEd aEOnlUsD2z4iYPhzP6Cw3tGaeqOf6WM= X-Google-Smtp-Source: AKy350biiA9lvuphIRYMJFwtuG7kLQs+hjCFiJ6xTxrxuaEKM3JVqYSi5eM7yAeBl5ERJLzEJp7S6Q== X-Received: by 2002:a17:903:294c:b0:1a2:8866:e8a4 with SMTP id li12-20020a170903294c00b001a28866e8a4mr6536899plb.1.1681949659847; Wed, 19 Apr 2023 17:14:19 -0700 (PDT) Received: from squeak.grove.modra.org (158.106.96.58.static.exetel.com.au. [58.96.106.158]) by smtp.gmail.com with ESMTPSA id a7-20020a1709027d8700b001a653a32173sm53773plm.29.2023.04.19.17.14.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 19 Apr 2023 17:14:19 -0700 (PDT) Received: by squeak.grove.modra.org (Postfix, from userid 1000) id 01222114084F; Thu, 20 Apr 2023 09:44:16 +0930 (ACST) Date: Thu, 20 Apr 2023 09:44:16 +0930 From: Alan Modra To: Andrew Pinski Cc: binutils@sourceware.org Subject: Re: Is aarch64_be-linux-gnu_ilp32 supported? Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-3029.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Wed, Apr 19, 2023 at 04:41:53PM -0700, Andrew Pinski wrote: > On Wed, Apr 19, 2023 at 4:34 PM Alan Modra via Binutils > wrote: > > > > 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. > > The Linux kernel support for ILP32 never made it upstream; glibc > support never made it upstream; though there was a branch on > sourceware.org at one time. And we (the folks who were working on > ILP32 at the time) never tested big-endian support. Thanks for the info. I only chose aarch64_be-linux-gnu_ilp32 because I hadn't previously tested any aarch64 BE targets. Having just now tested aarch64-linux-gnu_ilp32 and getting these results, FAIL: binutils-all/aarch64/sve-dwarf-registers FAIL: Disassembler detects unallocated instruction encodings. FAIL: binutils-all/strip-14 FAIL: binutils-all/strip-15 FAIL: gas/aarch64/reloc-prel_g1_nc FAIL: gas/aarch64/reloc-prel_g2 FAIL: gas/aarch64/reloc-prel_g2_nc FAIL: gas/aarch64/reloc-prel_g3 FAIL: gas/aarch64/symbol-variant_pcs-1 FAIL: ld-aarch64/erratum843419_tls_ie FAIL: ld-aarch64/erratum843419-far-adr FAIL: ld-aarch64/erratum843419-far-full FAIL: ld-aarch64/emit-relocs-257 FAIL: aarch64-farcall-back FAIL: aarch64-farcall-b-gsym FAIL: aarch64-farcall-group FAIL: ld-aarch64/tls-relax-all FAIL: ld-aarch64/tls-relax-gd-le FAIL: ld-aarch64/tls-relax-gdesc-le FAIL: ld-aarch64/tls-relax-gdesc-le-now FAIL: ld-aarch64/tls-relax-ie-le FAIL: ld-aarch64/tls-relax-ld-le-small FAIL: ld-aarch64/tls-relax-ld-le-tiny FAIL: ld-aarch64/tls-desc-ie FAIL: ld-aarch64/tls-relax-gdesc-le-2 FAIL: ld-aarch64/tls-relax-ie-le-2 FAIL: ld-aarch64/tls-relax-ie-le-3 FAIL: ld-aarch64/tls-tiny-gd FAIL: ld-aarch64/tls-tiny-gd-le FAIL: ld-aarch64/tls-tiny-desc FAIL: ld-aarch64/tls-tiny-desc-le FAIL: ld-aarch64/tls-tiny-ie FAIL: ld-aarch64/tls-tiny-ld FAIL: ld-aarch64/tls-small-ld FAIL: ld-aarch64/tlsle-symbol-offset FAIL: ld-aarch64/gc-got-relocs FAIL: ld-aarch64/gc-tls-relocs FAIL: TLS offset out of range FAIL: TLS offset out of range - TPREL_ADD_LO12 FAIL: ld-aarch64/protected-data FAIL: ld-aarch64/tls-relax-gd-ie FAIL: ld-aarch64/tls-relax-large-gd-ie FAIL: ld-aarch64/tls-relax-large-desc-ie FAIL: ld-aarch64/tls-relax-gdesc-ie FAIL: ld-aarch64/tls-relax-gdesc-ie-2 FAIL: ld-aarch64/tls-tiny-gd-ie FAIL: ld-aarch64/tls-tiny-desc-ie FAIL: ld-aarch64/tls-relax-gd-ie-2 FAIL: ld-aarch64/tls-relax-gd-ie-3 FAIL: ld-aarch64/tls-relax-ie-le-4 FAIL: ld-aarch64/relasz FAIL: AArch64 mapping symbol for plt section test. FAIL: GNU Property (single input, combine section) FAIL: GNU Property (combine multiple with BTI) FAIL: GNU Property (combine multiple with PAC) FAIL: PT_GNU_PROPERTY alignment FAIL: Check -z force-bti emits BTI PLT (shared) FAIL: Check -z force-bti emits BTI feature (shared) FAIL: ld-aarch64/exe with copy relocation FAIL: ld-aarch64/exe with copy relocation 2 FAIL: ld-aarch64/exe with copy relocation elimination FAIL: ld-aarch64/func sym hash opt for exe FAIL: Build bti-plt-so for PLT tests FAIL: Check -z force-bti emits BTI PLT (exec) FAIL: Check -z force-bti emits BTI feature (exec) FAIL: BTI PLT with only GNU PROP FAIL: Warn with one missing GNU NOTE BTI input FAIL: Warn when neither inputs has GNU NOTE BTI FAIL: ld-aarch64/pac-plt-1 FAIL: ld-aarch64/pac-plt-2 FAIL: ld-aarch64/bti-pac-plt-1 FAIL: ld-aarch64/bti-pac-plt-2 FAIL: Warn when both have GNU prop but neither BTI FAIL: ld-aarch64/weak-tls FAIL: ld-aarch64/undef-tls FAIL: Check linker stubs with indirect calls handle BTI (shared lib). FAIL: Check linker stubs with indirect calls handle BTI (exe). FAIL: Check linker stubs with indirect calls handle BTI when target has BTI. the message is fairly loud and clear that this is an experimental target. BTW, aarch64_be-linux-gnu gets the same segfaults I was seeing with aarch64_be-linux-gnu_ilp32. -- Alan Modra Australia Development Lab, IBM