https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108644
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Jan Dubiec from comment #5) > Regarding gcc/ira-conflicts.cc, I think you are probably right, parentheses > should fix the issue. But I am not able to understand (without looking into > docs) how without the parentheses the expressions are promoted to unsigned > long long int instead of just long int. And why the warning does not appear > on Linux. (long) allocated_words_num * sizeof (IRA_INT_TYPE) For Linux, it is (long) * (unsigned long) or (long) * (unsigned int) [first is LP64 and the second is ILP32], the first gives unsigned long while the second case gives long. While under LLP64LI32, you have (long) * (unsigned long long) so you get "unsigned long long" as the type. as sizeof returns size_t. Does that make sense now?
