Rif.: non-sequential order of build output

[Wolfgang]

Hello,

so far I had the impression that warning and error messages in the build output window are sorted by line numbers - until today I found an exception...

it is the first file in the project, subsequent files behave normally

[carlox]

In your case, it's likely this happens because compiler detects the unused variables when the variables scope ends. You have two variables defined in different lines (I suppose) and compiler treats them in the order it prefers, may be in LIFO order (they are stack based auto variable, it make senses, it isn't ?).
Too lazy to test it on my PC...