public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/90599] Inefficient code for __builtin_memset
       [not found] <bug-90599-4@http.gcc.gnu.org/bugzilla/>
@ 2021-08-02 17:52 ` hjl.tools at gmail dot com
  0 siblings, 0 replies; only message in thread
From: hjl.tools at gmail dot com @ 2021-08-02 17:52 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90599

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|NEW                         |RESOLVED

--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
Fixed for GCC 12 with r12-285:

commit 985b3a6837dee7001e6b618f073ed74f0edf5787
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Mon Jun 10 09:57:15 2019 -0700

    Generate offset adjusted operation for op_by_pieces operations

    Add an overlap_op_by_pieces_p target hook for op_by_pieces operations
    between two areas of memory to generate one offset adjusted operation
    in the smallest integer mode for the remaining bytes on the last piece
    operation of a memory region to avoid doing more than one smaller
    operations.

    Pass the RTL information from the previous iteration to m_constfn in
    op_by_pieces operation so that builtin_memset_[read|gen]_str can
    generate the new RTL from the previous RTL.

*** This bug has been marked as a duplicate of bug 90773 ***

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2021-08-02 17:52 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-90599-4@http.gcc.gnu.org/bugzilla/>
2021-08-02 17:52 ` [Bug target/90599] Inefficient code for __builtin_memset hjl.tools at gmail dot com

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).