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 74C343857341; Tue, 30 May 2023 07:57:26 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 74C343857341
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1685433446;
	bh=xICQkZjvO1SXtGt00Hde/yNrWdUHb5pQN3Ydj6kFo6o=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Nc3W3T1Sxh8UvShkNO9EKHABPPmd8/KojEaTCd/s0lAe2+yHbcY5Sd+L90cDEH1WP
	 sX23FDZNBTIrBr04yzJfLpHaoqHMesuCVuzf2X0rMm82Sx5VyeUiBuw/32XUtFR64b
	 Gg/H3O3KncQs6iyHLm9bw38JxMYd0BmDcbzljJlU=
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109982] csmith: x86_64: znver1 issues
Date: Tue, 30 May 2023 07:57:26 +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: unknown
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109982-4-eGzyIoppeY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109982-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109982-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=3D109982

--- Comment #14 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Alexander Monakov from comment #13)
> David, did you somehow configure CSmith to emit attributes it wouldn't em=
it by default?

Yes. Flag --compiler-attributes.

I went through the list of csmith compiler flags which are switched off by
default. --float, --int128, --uint128 were the other ones.

I tried those three out and got many runtime differences. So many that I am
waiting for the current set of csmith problems I have found to be resolved,
before reporting the new set.

> Emitting random attributes makes sense for testing
> error recovery (gcc shouldn't ICE on nonsensical attribute combinations),
> but less so for checking correctness of generated code, as we see here.

It's quite possible that flag --compiler-attributes doesn't work all that w=
ell,
so it was switched off. I am happy to switch it off in future.=