From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) by sourceware.org (Postfix) with ESMTPS id E5D6C3858C2C for ; Fri, 22 Apr 2022 14:32:19 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E5D6C3858C2C Received: by mail-wm1-x336.google.com with SMTP id v64-20020a1cac43000000b0038cfd1b3a6dso8075634wme.5 for ; Fri, 22 Apr 2022 07:32:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=2+eV45pFda+9VVvaYjetVsUX+WaAPn/no7QODuFycVM=; b=NKZLztAX/zmVg4YfnFqGeV8ow4DxGhj08EWZNv8QT49SA1pmMGPQLsHpkr5kqH63Rb M1RxzlYNWTCuqOlRC4zMKNgk7eF179Lica/iu7twPKEQJEPhHXjJm3iTcS02L36agGFT 1w4Vj9Skz0jT/2hovviq4omoSeof3cvcyNyTd+V9UGtllS1PSkq8zZPVvkvYzG6yGAAC UOlBq4RMbBF2LeU829Yii5oO9IIuRYGsNlHZL7HDljWztpUR2ppIknRv4xDrc5jK6lfk Hs75sRnp5Pfmbsak+0nXxJBBKko0wcPzZLxOquO/sWovDda1l+z6ooIxxbYHct6UnqpA xt6g== X-Gm-Message-State: AOAM530zGjbvnVQGZ/BQEIAdXE6TSDQfMKWtam4gosg3+p0EpHomE8Pl X0RMeTyZJj24WTBebjASxT2Lv/jbty4UswpmS1E= X-Google-Smtp-Source: ABdhPJy+yeWMHHzqk5MRij/do44oMfopN/iX1hlCJKYlCQ0RjU+z5zE2F/2mSSZQjtpHeIj1OpYQCv4AtscG2a0vMV8= X-Received: by 2002:a05:600c:4f53:b0:392:e99:3002 with SMTP id m19-20020a05600c4f5300b003920e993002mr4472821wmq.35.1650637938604; Fri, 22 Apr 2022 07:32:18 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jonathan Wakely Date: Fri, 22 Apr 2022 15:32:07 +0100 Message-ID: Subject: Re: Do not perform tests that are not supported by the CPU. To: sajcho Cc: gcc-help Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2022 14:32:21 -0000 On Fri, 22 Apr 2022 at 14:18, sajcho via Gcc-help wr= ote: > > Hi. > > lscpu output: > > Architecture: aarch64 > CPU op-mode(s): 32-bit, 64-bit > Byte Order: Little Endian > CPU(s): 6 > On-line CPU(s) list: 0,3-5 > Off-line CPU(s) list: 1,2 > Vendor ID: ARM > Model name: Cortex-A57 > Model: 3 > Thread(s) per core: 1 > Core(s) per cluster: 4 > Socket(s): - > Cluster(s): 1 > Stepping: r1p3 > CPU max MHz: 2035,2000 > CPU min MHz: 960,0000 > BogoMIPS: 62.50 > Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid > Caches (sum of all): > L1d: 128 KiB (4 instances) > L1i: 192 KiB (4 instances) > L2: 2 MiB (1 instance) > NUMA: > NUMA node(s): 1 > NUMA node0 CPU(s): 0,3-5 > Vulnerabilities: > Itlb multihit: Not affected > L1tf: Not affected > Mds: Not affected > Meltdown: Mitigation; PTI > Spec store bypass: Not affected > Spectre v1: Mitigation; __user pointer sanitization > Spectre v2: Mitigation; Branch predictor hardening, BHB > Srbds: Not affected > Tsx async abort: Not affected > > ../configure --prefix=3D/usr --libexecdir=3D/usr/lib --enable-languages= =3Dc,c++,fortran,lto --enable-threads=3Dposix --enable-__cxa_atexit --enabl= e-default-pie --enable-default-ssp --enable-linker-build-id --enable-initfi= ni-array --enable-link-serialization=3D1 --enable-gnu-indirect-function --e= nable-plugin --disable-nls --disable-multilib --disable-sjlj-exceptions --d= isable-libunwind-exceptions --disable-libquadmath-support --disable-libquad= math --with-system-zlib --with-linker-hash-style=3Dgnu --with-build-config= =3Dbootstrap-lto --with-pkgversion=3DSAUX-Aarch64 --build=3Daarch64-unknown= -linux-gnu --host=3Daarch64-unknown-linux-gnu > > make profiledbootstrap > > This is where my question begins. > Is there any easy way to avoid tests (sve, sve2, aapcs ....) that are not= supported by this cpu? In theory you shouldn't need to do anything. Tests that use those features should be restricted to only run when the CPU supports them, via https://gcc.gnu.org/onlinedocs/gccint/Effective-Target-Keywords.html#AA= rch64-specific-attributes In practice, some tests might not use the correct keywords to ensure that happens. Have you tried it?