public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105651] [12/13 Regression] bogus "may overlap" memcpy warning with std::string and operator+ at -O3
Date: Tue, 26 Jul 2022 10:46:22 +0000	[thread overview]
Message-ID: <bug-105651-4-fZ2OPNTVQW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105651-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 26 Jul 2022, jakub at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
> 
> --- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> My preference would be still to make the overlap case out-of-line as mentioned
> in PR105329, but I don't have statistics on whether the overlap case is really
> cold in real-world.  If yes, it would make non-overlap case smaller and the
> overlap case tiny bit slower.

I would say so.  It's of course still beneficial to optimize the
overlap test if possible.  I'm now testing a series of changes required.

  parent reply	other threads:[~2022-07-26 10:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 23:38 [Bug c++/105651] New: Failure compiling constexpr/__builtin_memcpy on Cygwin with -std=c++20 mckelvey at maskull dot com
2022-05-18 23:41 ` [Bug c++/105651] " mckelvey at maskull dot com
2022-05-19  0:10 ` [Bug tree-optimization/105651] bogus "may overlap" memcpy warning with std::string pinskia at gcc dot gnu.org
2022-05-19  6:19 ` rguenth at gcc dot gnu.org
2022-05-24 17:48 ` mckelvey at maskull dot com
2022-06-07 14:58 ` jens.maurer at gmx dot net
2022-06-21 17:33 ` pinskia at gcc dot gnu.org
2022-06-21 17:34 ` [Bug tree-optimization/105651] [12/13 Regression] " pinskia at gcc dot gnu.org
2022-06-21 17:38 ` pinskia at gcc dot gnu.org
2022-07-08 11:56 ` [Bug tree-optimization/105651] [12/13 Regression] bogus "may overlap" memcpy warning with std::string and operator+ at -O3 marxin at gcc dot gnu.org
2022-07-19 23:10 ` pinskia at gcc dot gnu.org
2022-07-26  9:57 ` rguenth at gcc dot gnu.org
2022-07-26 10:16 ` redi at gcc dot gnu.org
2022-07-26 10:20 ` jakub at gcc dot gnu.org
2022-07-26 10:36 ` redi at gcc dot gnu.org
2022-07-26 10:46 ` rguenther at suse dot de [this message]
2022-07-26 12:19 ` rguenth at gcc dot gnu.org
2022-08-03  9:57 ` redi at gcc dot gnu.org
2022-10-19 10:11 ` rguenth at gcc dot gnu.org
2022-10-19 10:48 ` redi at gcc dot gnu.org
2022-10-19 11:08 ` [Bug tree-optimization/105651] [12 " rguenth at gcc dot gnu.org
2022-12-12 10:24 ` rguenth at gcc dot gnu.org
2023-02-13 11:32 ` jg at jguk dot org
2023-04-20  4:44 ` pinskia at gcc dot gnu.org
2023-04-20 12:00 ` redi at gcc dot gnu.org
2023-05-08 12:24 ` rguenth at gcc dot gnu.org
2023-06-21 12:18 ` cvs-commit at gcc dot gnu.org
2023-06-21 12:22 ` redi at gcc dot gnu.org

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-105651-4-fZ2OPNTVQW@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).