There is no warning because the expression:
((uint32_val >> 8) & 0x000000FF)
is always convertible to a type that fits in a byte. Your uint32_val is not cast, but takes part in a calculation. The compiler can optimize this, and in this case it is clear the result after bit-wise and-ing with 000000ff
will always fit the provided l-value type, hence no warning.