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 B163E3858C60; Mon, 13 Mar 2023 21:50:28 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B163E3858C60
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1678744228;
	bh=hJVQjZV7qjlj3Cy4wa9nINbXhr8X+v1k+Ac+93fFnF0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=sOD001YmgvTAc37RDYqvXV+5SPWLp57APIlszhB8QqZ1iT0Bw1L6EX5FVBaRtlGTr
	 Zt0qhRWLFaYJtlI+bP/z7Z3shKksKjFCu592GknvXm2v/4XCpiPT5VpJtyiqKleYpo
	 rwmJZAtwX4QcX3wnLz+rvvRLrAyoVFneXKvMx2bA=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109109] [13 Regression] mariadb fails in tests on i586
 (non-LTO mode) after r13-4435-g2c089640279614e3
Date: Mon, 13 Mar 2023 21:50:28 +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: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109109-4-ZH60MCA7pG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109109-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109109-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=3D109109

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Martin Li=C5=A1ka from comment #4)
> > Another possible way to narrow it down a little bit would be to undo the
> > i386.md hunks from that commit one by one and see which one it is, all =
the 4
> > changes are optimizations and all of them are independent of each other=
 (any
> > of them dependent on the i386-expand.cc change which shouldn't change
> > anything on its own).
>=20
> All right, I was able to revert 3/4 of the hunks in i386.md and the
> problematic one that caused the miscompilation is:
>=20
> (define_insn_and_split "*concat<mode><dwi>3_3"
>   [(set (match_operand:<DWI> 0 "nonimmediate_operand" "=3Dro,r,r,&r")
> 	(any_or_plus:<DWI>
> 	  (ashift:<DWI>
> 	    (zero_extend:<DWI>
> 	      (match_operand:DWIH 1 "nonimmediate_operand" "r,m,r,m"))
> 	    (match_operand:<DWI> 2 "const_int_operand"))
> 	  (zero_extend:<DWI>
> 	    (match_operand:DWIH 3 "nonimmediate_operand" "r,r,m,m"))))]
>   "INTVAL (operands[2]) =3D=3D <MODE_SIZE> * BITS_PER_UNIT"
>   "#"
>   "&& reload_completed"
>   [(clobber (const_int 0))]
> {

Does using only that single hunk vs. no hunk at all narrow down further the
list of changed functions?=