From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id E7F523857C5B; Tue, 13 Feb 2024 21:52:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E7F523857C5B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1707861172;
	bh=0Z4URemdXj4wtSiYxzXcQdWI0wAGlUiNUB8r3uUfj0I=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=wxBRqIlN/EkQH+ySWCnzvDVbDrdFqUcpx7GiUU8KuzZ54j0E3TNPuoQQ2i9tAj485
	 qW8hkjxWXNB1SbOorKDrzvp5re+EGYvxhJsvtlvZuFkn/Mh5LuSAvsLDaEs+4IkDmi
	 jDiTzbAmPOyWpHmMA4iAEcuHgMc3neJ2FYPIvowQ=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/113899] Vect module test failures while running on
 remote host due to default dg-do set to compile and additional-sources being
 used
Date: Tue, 13 Feb 2024 21:52:52 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 13.2.0
X-Bugzilla-Keywords: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113899-4-yAkuPyIOs0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113899-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113899-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113899

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note I do think there is something wrong with your remote testing too but t=
hat
is only slightly related.

check_sse_hw_available should still be returning 1 there since SSE should
always be available for x86_64-linux. You might want to check the full log =
to
see why check_sse_hw_available is not working.  Maybe it is not picking up =
the
libraries or something like that.

Maybe the run testcases are failing but you might not be noticing that.=