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 63B0A3858000; Wed, 31 May 2023 13:54:43 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 63B0A3858000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1685541283;
	bh=/zFC1HYDeoo23f3wBE2CEIK1U6N5ArrKR02uC2KBbek=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=s1477ZnAF99U7lEo5J7TLjpDwqh9ECJJBwAAk1L7kljOMiqYULaqytUHavQWfgb0S
	 fwv8rVEejy6geNNhouhVRmIAgozyBm3RjiqhzTtqFi45/SlBnhSQvXCY07Dtxx/piQ
	 gDnq252EyetWZjngytt2j/sgq3uxqw0ianb/JMBc=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110059] When SPEC is used to test the GCC (10.3.1), the
 test result of subitem 548 fluctuates abnormally.
Date: Wed, 31 May 2023 13:54:43 +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: 10.3.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
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-110059-4-XkKTiiRftF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110059-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=3D110059

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'd like to point out that doing performance testing for GCC 10 at this poi=
nt
isn't a very good idea, GCC 10 is going out of support within a month or tw=
o,
and while some important wrong-code generation bugs can be still fixed ther=
e,
it is very unlikely any performance related bugs would be fixed there.  Of
course, if you find a performance problem with GCC 13 or even better trunk
compared to GCC 9 or older and then bisect it to a particular change, it is
helpful.=