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 F225A3858C2A; Tue,  5 Dec 2023 12:47:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F225A3858C2A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1701780456;
	bh=O1C77uSOBPCs/+NjeK5Z2fT1tlcTzzz9KBT0wNw9EFY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=VUX/y9ZKji5bz77I51ff1KQKhnsgtR87np6tk8ch8Mm5xh8JWK5PxlZ4krH6H8FSC
	 /HjdnJ4O58KkHZ79qAoELeQgEp7NAzCt7pQqCTfDJT17F7dWEAWEEKgbQHWvSN8Hfm
	 yoTgKqPE3lskL8R0wwiqgRxPozXLcQcBj29NjUFo=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87325] determine_base_object does not
 consider consider address space of base expr
Date: Tue, 05 Dec 2023 12:47:35 +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: 9.0
X-Bugzilla-Keywords: addr-space, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: bug_status cf_reconfirmed_on
Message-ID: <bug-87325-4-o4hVA3EXEb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87325-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87325-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=3D87325

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
   Last reconfirmed|2018-09-17 00:00:00         |2023-12-5

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
It now works "better":

  <bb 3> [local count: 201326592]:
  ivtmp.7_24 =3D (<unnamed-unsigned:24>) &ts;

  <bb 4> [local count: 805306368]:
  # i_20 =3D PHI <i_15(6), 0(3)>
  # ivtmp.7_26 =3D PHI <ivtmp.7_25(6), ivtmp.7_24(3)>
  _29 =3D (<address-space-7> void *) ivtmp.7_26;
  _30 =3D _29 + 4;
  _1 =3D MEM[(float *)_30];
  _2 =3D MEM[(float *)_29];
  _3 =3D bar (_2, _1);
  r =3D _3;
  _17 =3D ivtmp.7_26 + 8;
  _4 =3D (const <address-space-7> float *) _17;
  _5 =3D (const float *) _4;
  _6 =3D foo (&r, _5);
  if (_6 !=3D 0)

note the (implicit) address-space convert for the 2nd argument to foo (),
the testcase may be actually invalid.  The linked bug is still there,
but this one might be fixed by r14-6133-ge00c00730912cd?

Please verify and close if fixed.  PR60075 tracks a remaining IVOPTs issue.=