[Python-bugs-list] [Bug #132597] 2.1a2 compiler warnings on Compaq Tru64 Unix
noreply@sourceforge.net
noreply@sourceforge.net
Mon, 19 Feb 2001 13:55:59 -0800
Bug #132597, was updated on 2001-Feb-15 12:35
Here is a current snapshot of the bug.
Project: Python
Category: Build
Status: Open
Resolution: None
Bug Group: Platform-specific
Priority: 5
Submitted by: mfavas
Assigned to : akuchling
Summary: 2.1a2 compiler warnings on Compaq Tru64 Unix
Details: 2.1a2 from CVS of Feb 16 produces the following compiler warnings
on Tru64
Unix (uname -a: OSF1 gonzo.per.dem.csiro.au V4.0 1229 alpha, Compaq C
compiler, version: Compaq C V6.3-129 (dtk), Compiler Driver V6.3-126
(dtk)):
cc -c -O -Olimit 1500 -I. -I./Include -DHAVE_CONFIG_H -o Python/ceval.o
Python/ceval.c
cc: Info: Python/ceval.c, line 327: Trailing comma found in enumerator
list. (trailcomma)
};
cc -O -Olimit 1500 -I. -I./Include -IInclude/ -I/usr/local/include -c
Modules/_cursesmodule.c -o build/temp.osf1-V4.0-alpha-2.1/_cursesmodule.o
cc: Warning: Modules/_cursesmodule.c, line 632: In this statement,
"derwin(...)" of type "int", is being converted to "pointer to struct
_win_st". (cvtdiftypes)
win = derwin(self->win,nlines,ncols,begin_y,begin_x);
cc: Warning: Modules/_cursesmodule.c, line 1287: In this statement,
"subpad(...)" of type "int", is being converted to "pointer to struct
_win_st". (cvtdiftypes)
win = subpad(self->win, nlines, ncols, begin_y, begin_x);
cc: Warning: Modules/_cursesmodule.c, line 1517: In this statement,
"termname(...)" of type "int", is being converted to "pointer to const
char". (cvtdiftypes)
NoArgReturnStringFunction(termname)
cc: Warning: Modules/_cursesmodule.c, line 1686: In this statement,
"getwin(...)" of type "int", is being converted to "pointer to struct
_win_st". (cvtdiftypes)
win = getwin(PyFile_AsFile(temp));
cc: Warning: Modules/_cursesmodule.c, line 1954: In this statement,
"keyname(...)" of type "int", is being converted to "pointer to const
char". (cvtdiftypes)
knp = keyname(ch);
cc: Warning: Modules/_cursesmodule.c, line 2245: In this statement,
"tigetstr(...)" of type "int", is being converted to "pointer to char".
(cvtdiftypes)
capname = tigetstr( capname );
cc: Warning: Modules/_cursesmodule.c, line 2270: In this statement,
"tparm(...)" of type "int", is being converted to "pointer to char".
(cvtdiftypes)
result = tparm(fmt);
cc: Warning: Modules/_cursesmodule.c, line 2273: In this statement,
"tparm(...)" of type "int", is being converted to "pointer to char".
(cvtdiftypes)
result = tparm(fmt,i1);
cc: Warning: Modules/_cursesmodule.c, line 2276: In this statement,
"tparm(...)" of type "int", is being converted to "pointer to char".
(cvtdiftypes)
result = tparm(fmt,i1,i2);
cc: Warning: Modules/_cursesmodule.c, line 2279: In this statement,
"tparm(...)" of type "int", is being converted to "pointer to char".
(cvtdiftypes)
result = tparm(fmt,i1,i2,i3);
cc: Warning: Modules/_cursesmodule.c, line 2282: In this statement,
"tparm(...)" of type "int", is being converted to "pointer to char".
(cvtdiftypes)
result = tparm(fmt,i1,i2,i3,i4);
cc: Warning: Modules/_cursesmodule.c, line 2285: In this statement,
"tparm(...)" of type "int", is being converted to "pointer to char".
(cvtdiftypes)
result = tparm(fmt,i1,i2,i3,i4,i5);
cc: Warning: Modules/_cursesmodule.c, line 2288: In this statement,
"tparm(...)" of type "int", is being converted to "pointer to char".
(cvtdiftypes)
result = tparm(fmt,i1,i2,i3,i4,i5,i6);
cc: Warning: Modules/_cursesmodule.c, line 2291: In this statement,
"tparm(...)" of type "int", is being converted to "pointer to char".
(cvtdiftypes)
result = tparm(fmt,i1,i2,i3,i4,i5,i6,i7);
cc: Warning: Modules/_cursesmodule.c, line 2294: In this statement,
"tparm(...)" of type "int", is being converted to "pointer to char".
(cvtdiftypes)
result = tparm(fmt,i1,i2,i3,i4,i5,i6,i7,i8);
cc: Warning: Modules/_cursesmodule.c, line 2297: In this statement,
"tparm(...)" of type "int", is being converted to "pointer to char".
(cvtdiftypes)
result = tparm(fmt,i1,i2,i3,i4,i5,i6,i7,i8,i9);
cc: Warning: Modules/_cursesmodule.c, line 310: The scalar variable "arg1"
is fetched but not initialized. And there may be other such fetches of
this variable that have not been reported in this compilation. (uninit1)
Window_NoArg2TupleReturnFunction(getparyx, int, "(ii)")
cc: Warning: Modules/_cursesmodule.c, line 310: The scalar variable "arg2"
is fetched but not initialized. And there may be other such fetches of
this variable that have not been reported in this compilation. (uninit1)
Window_NoArg2TupleReturnFunction(getparyx, int, "(ii)")
cc: Warning: Modules/_cursesmodule.c, line 309: The scalar variable "arg1"
is fetched but not initialized. And there may be other such fetches of
this variable that have not been reported in this compilation. (uninit1)
Window_NoArg2TupleReturnFunction(getmaxyx, int, "(ii)")
cc: Warning: Modules/_cursesmodule.c, line 309: The scalar variable "arg2"
is fetched but not initialized. And there may be other such fetches of
this variable that have not been reported in this compilation. (uninit1)
Window_NoArg2TupleReturnFunction(getmaxyx, int, "(ii)")
cc: Warning: Modules/_cursesmodule.c, line 308: The scalar variable "arg1"
is fetched but not initialized. And there may be other such fetches of
this variable that have not been reported in this compilation. (uninit1)
Window_NoArg2TupleReturnFunction(getbegyx, int, "(ii)")
cc: Warning: Modules/_cursesmodule.c, line 308: The scalar variable "arg2"
is fetched but not initialized. And there may be other such fetches of
this variable that have not been reported in this compilation. (uninit1)
Window_NoArg2TupleReturnFunction(getbegyx, int, "(ii)")
Follow-Ups:
Date: 2001-Feb-19 13:55
By: fdrake
Comment:
Looks like a different header may be needed to pick up the prototypes for
many of these. Assigned to the curses module guy.
-------------------------------------------------------
Date: 2001-Feb-16 04:14
By: twouters
Comment:
The first warning is my mistake. I thought I fixed that in a more recent
version of my continue-inside-try patch, but apparently I didn't. Fixed in
revision 2.230 of Python/ceval.c
The warnings in Modules/_cursusmodule.c are most likely caused by undefined
functions, though why you don't see an error for those beats me. (undefined
functions default to int-returning functions, so that's probably why you
see those warnings.)
The *other* warnings look damned legit, though, and the only reason they
aren't is because getmaxyx and co. are (on the BSDI and Linux boxes I have
acces to) defined as being macro calls, and in fact they *have* to be macro
calls (or non-standard C calls) or they can't work. I'm not a curses
expert, but I think an initialization is in place here (or just rewriting
the silly macros so they make *sense* :-)
-------------------------------------------------------
For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=132597&group_id=5470