public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113049] Compiles to strlen even with -fno-builtin-strlen -fno-optimize-strlen
Date: Sun, 17 Dec 2023 15:33:17 +0000	[thread overview]
Message-ID: <bug-113049-4-yJm1W4BXyD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113049-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Georg-Johann Lay <gjl at gcc dot gnu.org> ---
(In reply to Andreas Schwab from comment #4)
> -fno-builtin-strlen has a different purpose.

So then -fno-builtin should also not work? GCC documentation of -fno-builtin is
the same like for -fno-builtin-function.

At least there should be an option to disable this, e.g. you need it when
building libgcc / libc anyway, you you get silly non-functional libs.

  parent reply	other threads:[~2023-12-17 15:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17  9:36 [Bug tree-optimization/113049] New: " gjl at gcc dot gnu.org
2023-12-17  9:39 ` [Bug tree-optimization/113049] " gjl at gcc dot gnu.org
2023-12-17 10:05 ` mikpelinux at gmail dot com
2023-12-17 14:24 ` gjl at gcc dot gnu.org
2023-12-17 15:10 ` schwab@linux-m68k.org
2023-12-17 15:33 ` gjl at gcc dot gnu.org [this message]
2023-12-17 16:47 ` schwab@linux-m68k.org
2023-12-17 17:10 ` gjl at gcc dot gnu.org
2023-12-17 17:28 ` harald at gigawatt dot nl
2023-12-17 17:58 ` pinskia 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-113049-4-yJm1W4BXyD@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).