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 tree-optimization/102958] std::u8string suboptimal compared to std::string, triggers warnings
Date: Thu, 25 Nov 2021 19:17:31 +0000	[thread overview]
Message-ID: <bug-102958-4-qVQrmEkSPu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102958-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2021-11-25
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed, interesting we don't detect this as strlen:
  <bb 3> [local count: 8687547547]:
  # __i_155 = PHI <__i_46(3), 0(2)>
  __i_46 = __i_155 + 1;
  _48 = MEM[(const char_type &)"123456789" + __i_46 * 1];
  if (_48 != 0)
    goto <bb 3>; [89.00%]
  else
    goto <bb 4>; [11.00%]

I thought there was code to do that dection now?

  parent reply	other threads:[~2021-11-25 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 22:37 [Bug tree-optimization/102958] New: " msebor at gcc dot gnu.org
2021-10-26 22:40 ` [Bug tree-optimization/102958] " msebor at gcc dot gnu.org
2021-11-19 18:16 ` cvs-commit at gcc dot gnu.org
2021-11-25 19:17 ` pinskia at gcc dot gnu.org [this message]
2021-12-09 23:24 ` cvs-commit at gcc dot gnu.org
2021-12-10 22:11 ` jason at gcc dot gnu.org
2024-01-09 14:32 ` [Bug tree-optimization/102958] std::u8string suboptimal compared to std::string aldyh at gcc dot gnu.org
2024-01-09 14:34 ` aldyh at gcc dot gnu.org
2024-01-09 14:37 ` 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-102958-4-qVQrmEkSPu@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).