increased occurance of "may be used uninitialized in this function"
|Created on||Jun 25, 2007 16:02|
|Resolved on||Jun 26, 2007 14:33|
since quite a while (maybe 3 months??) we see a rather significant increase in warnings of the kind: "may be used uninitialized in this function" It was anticipated that theese stem from the inlining bug (110). However, that anticipation is wrong. It has something to do with the code that is created whenever an AUD variable is assigned to a scalar value. See the attached example. In essence, the compiler creates a for loop for extracting the values which, in case the AUD value would be empty, results in an un-initialised variable. If we turn on -check tb the check comes in a rather diguised form so that the C compiler fails to find out that an empty for-loop in fact cannot happen. I am not sure what to do here. As a starting point one may try to find out why this problem did not occur earlier. Looking into the history of the masterrun might be a starting point to get an idea which compiler version did not yet suffer from the flooding by warnings.....
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information