From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 79CE53858D20 for ; Fri, 14 Apr 2023 10:25:19 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 79CE53858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1681467919; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=Fvvri5q7IKjOKollcaqxvCl+Gm+wgUrdy/8PEJBKJ68=; b=ImwoScQ6BRSLDYphWr6DyomhC6XB3hMRnrhiNWbp0tqawbuCP+HUVMruupJytMqgD3EilX VcIFZRzyiRidLz0t47sid8G7dIFiVkz9zdG7T1oM5B3GHvhEBQmJHYT7aIF98gZ4ptfVHf zD31SK6+AHGjCj1h3MzRMskzucMJgHg= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-47-ueNVUWSbNyG-dot7Wx_EZw-1; Fri, 14 Apr 2023 06:25:10 -0400 X-MC-Unique: ueNVUWSbNyG-dot7Wx_EZw-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B99C0886462; Fri, 14 Apr 2023 10:25:09 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.39.192.16]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 4A23B2166B26; Fri, 14 Apr 2023 10:25:09 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 33EAP6hI1926229 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Fri, 14 Apr 2023 12:25:06 +0200 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 33EAP5QW1926228; Fri, 14 Apr 2023 12:25:05 +0200 Date: Fri, 14 Apr 2023 12:25:05 +0200 From: Jakub Jelinek To: Richard Biener Cc: gcc-patches@gcc.gnu.org Subject: Re: [PATCH] Fix vect-simd-clone testcase dump scanning Message-ID: Reply-To: Jakub Jelinek References: <20230414094255.F02F313498@imap2.suse-dmz.suse.de> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,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 Fri, Apr 14, 2023 at 10:15:06AM +0000, Richard Biener wrote: > Oops. Indeed target_avx checks whether it can compile sth with > -O2 -mavx rather than verifying avx is present. I've seen scan > failures with -m32/-march=cascadelake on a zen2 host. I'm not exactly > sure why. That is strange. Sure, -march=cascadelake implies -mavx (-mavx512f even), but it would surprise me if on such a host avx_runtime wasn't true. But we've been there before, I think cascadelake turns on the vector epilogues. In r13-6784 I've added --param vect-epilogues-nomask=0 to some testcases that were affected at that point, but perhaps something is affected since then. Will have a look. Jakub