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 40EC13858D3C; Wed, 21 Feb 2024 04:27:37 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 40EC13858D3C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1708489658;
	bh=XTyWpZCSrluM0CTY7wm6xc7+FxpBLD3cM6LruyQNzXo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=xcOFLXX6bxeNXuiKGhKW4gXv1eq5ozpDgkLlROC9JwN3GLXneuJK9QPfLZDXxL8gK
	 a0sm3u22MfecDUdRbftSjpdaEDdRaicqq3p6Ldt9uUh9R1TYTOAFC0Txr/v1zCEZ1i
	 lYkSzz9l47JDHpJlqOFpyTKcCiOrSs9DutAKNCa0=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98563] [11/12/13/14 Regression] vectorization
 fails while it worked on gcc 9 and earlier since since
 r10-2271-gd81ab49d0586fca0
Date: Wed, 21 Feb 2024 04:27:36 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.1.0
X-Bugzilla-Keywords: missed-optimization, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.5
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-98563-4-lAn0i2ZenB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-98563-4@http.gcc.gnu.org/bugzilla/>
References: <bug-98563-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=3D98563

--- Comment #13 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Looking at this, I see in PRE:
  REALPART_EXPR <D.72413[_8]._M_value> =3D _25;
  IMAGPART_EXPR <D.72413[_8]._M_value> =3D _26;
  _19 =3D REALPART_EXPR <MEM <struct complex[16]> [(const struct complex
&)&D.72413][_8]._M_value>;

Should _19 be the same as _25 ?

I suspect if this is done, then the vectorizer would kick in and do the rig=
ht
thing.=