PATCH - Rid Glibc of "inlining failed" type warnings

Greg Schafer gschafer at zip.com.au
Sun Oct 19 16:35:31 PDT 2003


Hi

Dunno why I even did this.. I don't even use Glibc-2.3.2 anymore... 'cept
for testing book builds..


I really should have done this some time ago, so as to get it into the 5.0
book release. If there is no new Glibc release on the horizon, we can look
at including it later on.


------------------
Submitted By: Greg Schafer <gschafer at zip dot com dot au>
Date: 2003-10-20
Initial Package Version: 2.3.2
Origin: I backported these fixes directly from Glibc CVS HEAD.
Description: Dramatically reduce the number of "inlining failed" type
warnings.

This patch, when combined with -finline-limit=2000, reduces the number of
"inlining failed" type warnings from 3878 down to 28 (unique 309 down to 6). At 
the time Glibc-2.3.2 was released, Gcc-3.2.x was the preferred compiler.
Gcc-3.3.x introduced a new inliner which showed up a number of areas in the 
Glibc source that needed reviewing.

Glibc is largely maintained by 3 RH employees. Those guys know what they're
doing and have seen fit to include the -finline-limit=2000 flag in the RH spec
file for quite some time now. Thus there can be no doubts about the validity of
using this flag in my view. If using this patch, be sure to add it to your
CFLAGS, for example:

CFLAGS="-g -O2 -finline-limit=2000" ./configure..............

I tested this by compiling Glibc-2.3.2 with Gcc-3.3.2. Glibc test suite passed.
------------------

Greg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: glibc-2.3.2-inlining-fixes-1.patch.gz
Type: application/x-gunzip
Size: 4876 bytes
Desc: not available
URL: <http://lists.linuxfromscratch.org/pipermail/patches/attachments/20031020/e3cd82fc/attachment.bin>


More information about the patches mailing list