From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5747 invoked by alias); 2 Oct 2013 08:59:34 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 5692 invoked by uid 55); 2 Oct 2013 08:59:31 -0000 From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/56888] memcpy implementation optimized as a call to memcpy Date: Wed, 02 Oct 2013 08:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: NEW 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: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-10/txt/msg00095.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888 --- Comment #23 from rguenther at suse dot de --- On Wed, 2 Oct 2013, bernd.edlinger at hotmail dot de wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56888 > > --- Comment #22 from Bernd Edlinger --- > (In reply to Richard Biener from comment #21) > > -fno-tree-loop-distribute-patterns is the reliable way to not transform loops > > into library calls. > > Thanks! > > Adding this fixed the generated code: > > #pragma GCC optimize ("no-tree-loop-distribute-patterns") > > BTW their memset.c looks like this: > > externC void * > memset( void *s, int c, size_t n ) __attribute__ ((weak, alias("_memset"))); > > void * > _memset( void *s, int c, size_t n ) > { > while (...) > } I suspect this is the most common form - glibc also uses aliases but IIRC they are using global asms for them :/ The above would be still detectable with the new symbol table / alias handling in GCC 4.9 (and maybe 4.8, I'm not sure). So it may be worth special-casing the "direct recursion" case as a QOI measure.