Christopher Faylor cgf@redhat.com
Tue Oct 30 21:28:00 GMT 2001

[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,
>  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.


More information about the Cygwin-developers mailing list