This is the mail archive of the
mailing list for the GCC project.
Re: A (minor) doc problem?
- To: Alexandre Oliva <aoliva at redhat dot com>
- Subject: Re: A (minor) doc problem?
- From: Jack Lloyd <lloyd at acm dot jhu dot edu>
- Date: Fri, 17 Aug 2001 11:20:27 -0400 (EDT)
- Cc: <gcc at gcc dot gnu dot org>
> On Aug 15, 2001, Jack Lloyd <firstname.lastname@example.org> wrote:
> > In the GCC 3.0 info pages, the option -finline-limits is documented as
> > controlling how large of a function is inlined for functions explicetely
> > marked as being inline. However, it seems like this actually controls the
> > inlining of all functions
> I doubt it. Do you have a code snippet and a command-line that would
> demonstrate the problem? Make sure you're not using -O3, because this
> implies -finline.
I was actually using -O3. But playing around with -finline-limits, it
seemed to affect the code regardless (ie, -O3 -finline-limit=0, the code
runs slower; but nominally, since inline-limit only affects things marked
inline, that shouldn't happen, since most of the code is not marked inline
[unless these two things are interfering with each other somehow, I
I'll play around with it some more and see what it's actually doing.
> Oh, I recall this problem. It affected a subset of sparc32 boxes, and
> is fixed for 3.0.1.
> > some code was looking for strcmp and friends and couldn't find them,
> I don't recall this one.
I that case, I would guess that it probably came about because I was using
"make -k", something tried to include the generated limits file which
didn't exist, and everything got messed up.