From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3F4F03858C66; Sun, 1 Oct 2023 22:26:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3F4F03858C66 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1696199166; bh=G7A4pflnLNJDUn8TNCeHd2NlzY+PbRbf8mp9EpxXdps=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Wbq0MZHq3CqSRn1uHrq25YxiecxN8W21hx1GCtCCvZ31cCXLnhU1VaJYJAwQUuyTF NIqTWZ7ViLlQEOkovIj9j20IdTVozUedkcuKEheWt3ZLan98FwR8o1fTl80cRVJGwX Yn+/a+HthWOhS9/mYDm7cVQ4O7+e4MipCsl6P99k= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111657] Memory copy with structure assignment from named address space is not working Date: Sun, 01 Oct 2023 22:26:05 +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: 12.3.1 X-Bugzilla-Keywords: missed-optimization 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: keywords dependson everconfirmed cf_reconfirmed_on 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=3D111657 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Depends on|79649 | Ever confirmed|0 |1 Last reconfirmed| |2023-10-01 Status|UNCONFIRMED |NEW --- Comment #2 from Andrew Pinski --- This is unrelated to PR 79649 as IV-OPTS does nothing here. if we do `-mstringop-strategy=3Dloop`, it works fine but `-mstringop-strategy=3Dlibcall` is broken. Seems like the middle-end expansion for the copy for the libcall case does worse than the target specific loop. Now the backend could select the target specific loop for this rather than = the libcall case .... Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D79649 [Bug 79649] Memset pattern in named address space crashes compiler or gener= ates wrong code=