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/102725] -fno-builtin leads to call of strlen since r12-4283-g6f966f06146be768
Date: Sun, 17 Dec 2023 19:56:27 +0000 [thread overview]
Message-ID: <bug-102725-4-bqksPy2EK8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102725-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102725
--- Comment #12 from Georg-Johann Lay <gjl at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> You need -fno-tree-loop-distribution -fno-tree-loop-distribute-patterns to
> turn it off. There is another older bug about this for memcpy.
This is also a documentation issue.
Neither from the naming of that option nor from its documentation one can
concluse that it inhibits open-coded-foo -> foo transformations.
And IMO options that disable all builtin generations should be available on
single function basis, like -fno-auto-strlen or whatever.
Moreover, introducing a call to strlen in a function named "strlen" (or with
assembly name "strlen") is not very wise.
prev parent reply other threads:[~2023-12-17 19:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 8:18 [Bug tree-optimization/102725] New: [12 Regression] " marxin at gcc dot gnu.org
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 [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-102725-4-bqksPy2EK8@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).