I get a whole bunch of compiler warnings when compiling 
the stock Python-2.1 on SGI IRIX 6.5.11m.  These 
warnings are innocuous, but I feel that many of them 
should be fixed anyway.  I particularly dislike code 
where a goto or return is immediately followed by 
break.  There is just *no way* the flow of control can 
get to that break and I feel that it betrays 
uncertainty in the programmer.

Logged In: YES 
user_id=31435

Sjoerd, it would be much more helpful if you submitted a 
patch.  We don't have an SGI IRIX 6.5.11m box to compile 
on, so can't tell whether we've fixed anything.  We have 
a "no compiler warnings!" policy that I enforce under the 
Windows build, and so I don't see *any* warnings in the 2.1 
build.

I fixed the most egregious ones where fixes were obviously 
harmless, checked in as

mmapmodule.c new revision: 2.28
unicodeobject.c new revision: 2.86
tokenizer.c new revision: 2.50
ceval.c new revision: 2.240

Logged In: YES 
user_id=3066

Sjoerd, are you planning to follow up on this?  See Tim's
remarks.

Logged In: YES 
user_id=43607

Most of the code causing warnings has been fixed.
Remaining are warnings like "cast between pointer-to-object
and pointer-to-function" for which I don't know a fix
(except turning of this particular warning) and a bunch of
warnings in glmodule which is generated and for which it's
too much work to fix the generator script.