From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 35B2138187DB; Mon, 5 Dec 2022 11:24:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 35B2138187DB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1670239471; bh=UPSL1fJ7C5jzRkRF8T3tE8VKA8oYRHDaKA6jggUr1us=; h=From:To:Subject:Date:In-Reply-To:References:From; b=E5HNZyoYO5OS9NoXi+km8ldXAWNjxzMtrsDv3MqHYWyxW32RVvm92A2PJ4wr+nOgt nx1gnffQw2D76KlvxSkBNruaGTV2HXzJPv0kS1uP3Da6+3PZc+/1MD5iGaXq1gthDg RM47b2FQS9LLwRm5uTKDZkf0umw4m1tqCMiNODpc= From: "brjd_epdjq36 at kygur dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107551] __builtin_cpu_supports returns a negative integer for "x86-64" Date: Mon, 05 Dec 2022 11:24:30 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 12.2.0 X-Bugzilla-Keywords: patch, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: brjd_epdjq36 at kygur dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107551 --- Comment #13 from Brjd --- I am not sure how I can run only this patched test against the newly built = gcc. Would you post instruction how it is done. I know it can run in the build t= ree when building gcc itself, but never test it against the testsuite when read= y. I unpack the source, patch the test and then what next?=