Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=484591 Ralf Corsepius <rc040203@xxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rc040203@xxxxxxxxxx --- Comment #8 from Ralf Corsepius <rc040203@xxxxxxxxxx> 2009-02-10 04:50:19 EDT --- (In reply to comment #6) > As Ralf has demonstrated these warnings are usually a real issue, which only > shows on 64 bit systems. But usually these are in debug printf's and thus quite > often people don't care about fixing them. I agree this is not something which > we normally block reviews on. So I wont do that in this case either. Still this > something which really should be fixed, so consider this a should fix item. That's why I had labeled it "SHOULD". It's a classic of the 32bit->64bit portability problems. It is broken code which is guaranteed to be non-functional under certain conditions. The only question is when this bug will hit, not if this will this will hit. Due to the nature of size_t, such kind of bugs show when some variable will exceed sizeof(int) (4GB) or when some computations will be performed on size_t's. The former will usually only cause visible problems in "big use-cases", while the later usually shows as "corrupt output". -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review