[issue15181] importlib.h: suncc warnings

Stefan Krah added the comment: Antoine Pitrou wrote: > > +fprintf(outfile, "%d,", (unsigned int) data[i]); > > > > Hmm, "%u"? :) > > It doesn't change anything, since data[i] is between 0 and 255. > (unless C `int` is 8 bits on your computer, but I doubt it :-)) That's true, but

[issue15181] importlib.h: suncc warnings

Antoine Pitrou added the comment: Le lundi 25 juin 2012 à 15:47 +, Stefan Krah a écrit : > > +fprintf(outfile, "%d,", (unsigned int) data[i]); > > Hmm, "%u"? :) It doesn't change anything, since data[i] is between 0 and 255. (unless C `int` is 8 bits on your computer, but I do

[issue15181] importlib.h: suncc warnings

Stefan Krah added the comment: +fprintf(outfile, "%d,", (unsigned int) data[i]); Hmm, "%u"? :) -- ___ Python tracker ___ ___

[issue15181] importlib.h: suncc warnings

Antoine Pitrou added the comment: It should be fixed now! -- nosy: +pitrou resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue15181] importlib.h: suncc warnings

Roundup Robot added the comment: New changeset 6dc9472346de by Antoine Pitrou in branch 'default': Issue #15181: importlib bytecode is unsigned and shouldn't have negative numbers. http://hg.python.org/cpython/rev/6dc9472346de -- nosy: +python-dev _

[issue15181] importlib.h: suncc warnings

New submission from Stefan Krah : suncc complains about negative values that are assigned to unsigned char: "Python/importlib.h", line 3634: warning: initializer does not fit or is out of range: -125 "Python/importlib.h", line 3635: warning: initializer does not fit or is out of range: -125 [.