public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102725] New: [12 Regression] -fno-builtin leads to call of strlen since r12-4283-g6f966f06146be768
Date: Wed, 13 Oct 2021 08:18:35 +0000	[thread overview]
Message-ID: <bug-102725-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102725
           Summary: [12 Regression] -fno-builtin leads to call of strlen
                    since r12-4283-g6f966f06146be768
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: stefansf at linux dot ibm.com
  Target Milestone: ---

I noticed that in valgrind package, where they define their own standard
library functions.

$ cat strlen.c
#include <stddef.h>

size_t mystrlen ( const char* str )
{
   size_t i = 0;
   while (str[i] != 0) i++;
   return i;
}

int main(int argc, char **argv)
{
  return mystrlen (argv[0]);
}

$ gcc strlen.c  -O3  -fno-builtin -S && grep "call.*strlen" strlen.s
        call    strlen
        call    strlen

Before your revision, no strlen was called.

             reply	other threads:[~2021-10-13  8:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13  8:18 marxin at gcc dot gnu.org [this message]
2021-10-13  8:31 ` [Bug tree-optimization/102725] " pinskia at gcc dot gnu.org
2021-10-13  8:38 ` [Bug tree-optimization/102725] " marxin at gcc dot gnu.org
2021-10-13  8:46 ` pinskia at gcc dot gnu.org
2021-10-13 11:36 ` rguenth at gcc dot gnu.org
2021-12-29 13:11 ` marxin at gcc dot gnu.org
2022-07-18 22:44 ` pinskia at gcc dot gnu.org
2023-02-08 17:45 ` pinskia at gcc dot gnu.org
2023-06-03  0:42 ` vincent.riviere at freesbee dot fr
2023-06-03  1:16 ` pinskia at gcc dot gnu.org
2023-06-03  1:56 ` terra at gnome dot org
2023-12-17 17:58 ` pinskia at gcc dot gnu.org
2023-12-17 19:56 ` gjl 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-102725-4@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).