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/108715] Infinite loop in the generated assembly with -Os when strlen is defined in the code
Date: Wed, 08 Feb 2023 17:52:04 +0000	[thread overview]
Message-ID: <bug-108715-4-rBBXouW2EC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108715-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #14)
> It isn't really a dup, that other PR is about strlen pattern in some
> function with a different name.

PR 103858 was also marked as a dup much earlier.
I think the original code in valgrind (which PR 102725 is about) used strlen as
the name of the function and the reporter change the name just to show what was
happening ...

      parent reply	other threads:[~2023-02-08 17:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 10:29 [Bug c/108715] New: " daniel at eyoman dot com
2023-02-08 10:30 ` [Bug c/108715] " daniel at eyoman dot com
2023-02-08 10:30 ` daniel at eyoman dot com
2023-02-08 10:32 ` daniel at eyoman dot com
2023-02-08 10:33 ` daniel at eyoman dot com
2023-02-08 10:34 ` daniel at eyoman dot com
2023-02-08 10:34 ` daniel at eyoman dot com
2023-02-08 10:38 ` daniel at eyoman dot com
2023-02-08 11:27 ` [Bug middle-end/108715] " pinskia at gcc dot gnu.org
2023-02-08 11:34 ` daniel at eyoman dot com
2023-02-08 11:38 ` jakub at gcc dot gnu.org
2023-02-08 12:22 ` daniel at eyoman dot com
2023-02-08 12:37 ` jakub at gcc dot gnu.org
2023-02-08 17:45 ` pinskia at gcc dot gnu.org
2023-02-08 17:48 ` jakub at gcc dot gnu.org
2023-02-08 17:52 ` pinskia at gcc dot gnu.org [this message]

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-108715-4-rBBXouW2EC@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).