public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.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 [thread overview]
Message-ID: <bug-111657-4-vNibWWQE4S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111657-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111657
Andrew Pinski <pinskia at gcc dot gnu.org> 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 <pinskia at gcc dot gnu.org> ---
This is unrelated to PR 79649 as IV-OPTS does nothing here.
if we do `-mstringop-strategy=loop`, it works fine but
`-mstringop-strategy=libcall` 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=79649
[Bug 79649] Memset pattern in named address space crashes compiler or generates
wrong code
next prev parent reply other threads:[~2023-10-01 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 21:41 [Bug middle-end/111657] New: " ubizjak at gmail dot com
2023-10-01 21:57 ` [Bug middle-end/111657] " ubizjak at gmail dot com
2023-10-01 22:26 ` pinskia at gcc dot gnu.org [this message]
2023-10-01 22:31 ` [Bug target/111657] Memory copy with structure assignment from named address space should be improved pinskia at gcc dot gnu.org
2023-10-02 9:21 ` ubizjak at gmail dot com
2023-10-02 9:25 ` ubizjak at gmail dot com
2023-10-05 15:43 ` cvs-commit at gcc dot gnu.org
2023-10-05 15:46 ` ubizjak at gmail dot com
2023-11-17 12:07 ` jakub at gcc dot gnu.org
2023-11-17 13:39 ` ubizjak at gmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-111657-4-vNibWWQE4S@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).