From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 134AA3858C35; Sun, 3 Dec 2023 22:17:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 134AA3858C35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1701641859; bh=ry8MrjGDPo5cP1qwhzSLE367tALEHK/DZR20eUgGtyY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nCbfjOxLWLaAjEAn61FmtpymqlJ4VNf2Xjt1nEgcLcUd+cuKtsVLm2M1bOQbmr23M +fV577yBVmFKCj3W+ge2eg8ShvQByat2rKKYm3RfO7vCUTlRd7nABZDv3WacFD9WwN zhU4waU67sgTBqo5DigNmynPbpTjGOfA4bTZ5r1s= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/112830] internal compiler error: in convert_memory_address_addr_space_1, at explow.cc:302 Date: Sun, 03 Dec 2023 22:17:37 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: addr-space, ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: NEW 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: everconfirmed cf_reconfirmed_on cc bug_status Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112830 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2023-12-03 CC| |pinskia at gcc dot gnu.org Status|UNCONFIRMED |NEW --- Comment #2 from Andrew Pinski --- The middle-end of GCC definitely does not support the case where size_type = for address spaces is different from the original type. At this point as shown = by the other bug reports too. I had ideas of how to change/fix that but have n= ot implemented it since the targets recently I work on don't have that issue (= well don't have address spaces either). This work does require modifying almost all of the middle-end to support th= is. Did it get this support worse with the addition of pointer plus, yes but at= the same time it did get easier to implement.=