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
Message-ID:	<03b201c15b78$cac732e0$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	<cygwin-developers AT sourceware DOT cygnus DOT com>
Subject:	-finline-functions
Date:	Tue, 23 Oct 2001 14:11:28 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime:	23 Oct 2001 04:16:10.0419 (UTC) FILETIME=[71F5D030:01C15B79]

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.

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.

Rob

- Raw text -