From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 63B203858CD1; Sun, 17 Dec 2023 19:56:28 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 63B203858CD1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1702842988;
	bh=L7VwHWPkWSB6Ps0fDq78daQNNTuxgsZmon8g/5ogPIs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=DeD2X5NKernjNwJPCenoUG7S6WZJT9BWQgHxQ49RLAeKhv3D9iA2jxfFL5v7b49lc
	 U8ZRas89fBjVa+XxAuXJIBEiVxxHyjrf+lZ1vq+OmJkI8xyldCnNKu814j2yuZXMi4
	 Li0R6XPInmCN2NeN6kFT41pa0N0mZaix1daNk9ic=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gjl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-102725-4-bqksPy2EK8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-102725-4@http.gcc.gnu.org/bugzilla/>
References: <bug-102725-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- 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.=