Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Wed, 31 Oct 2001 00:29:52 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: -finline-functions
Message-ID: <20011031002952.B20902@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <03b201c15b78$cac732e0$0200a8c0 AT lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <03b201c15b78$cac732e0$0200a8c0@lifelesswks>
User-Agent: Mutt/1.3.21i

[a delayed response]
On Tue, Oct 23, 2001 at 02:11:28PM +1000, Robert Collins wrote:
>new thread time I think.
>
>I just built cygwin with -Winline as part of looking at this. There are
>a number of warnings, that I haven't looked into - and won't for now -
>but it is educational.

I added this to Makfile.in.  gcc 3.x doesn't seem to warn about anything.
gcc 2.95.3 has some very disappointing warnings.

>Jonathon: When working on a -O3 cygwin, I suggest you turn on some more
>warning flags than cygwin builds with by default.
>
>AFAIK some of the things that gcc does when optimising are more likely
>to go wrong if a warning would have been produced.
>
>>From a performance viewpoint, it's helpful to know when things are not
>being optimised as we've hinted.
>
>For example,
>this:
>  inline const PSID operator= (const PSID nsid)
>    { return assign (nsid); }
>
>isn't inlined which might be a surprise. I haven't checked yet but I
>believe it's the nested assign() call that prevents this inlining.

I noticed a couple of other inline candidates who couldn't inline for
what I assume is the same reason.

cgf