It happens at certain point the file will look like this:
#define UINT16BIT unsigned short int
#define UINT32BIT unsigned int
#define PIXEL_PER_STRIPE 0
#define BS 1024
#define DIM_X 0
#define DIM_Y 0
#define STRIPES_PER_BS 0
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
unsigned short detectSaturation_saturationLimit;
void detectSaturation(UINT16BIT frame[][DIM_X][BS][BS], UINT16BIT saturationLimit, UINT32BIT saturationFrame[][DIM_X][BS][BS / 32], int i, int j) {
UINT32BIT x, y, stripe;
UINT16BIT saturationLimitValue;
UINT32BIT stripe_lb = j * STRIPES_PER_BS;
for (stripe = stripe_lb;
stripe < stripe_lb + STRIPES_PER_BS;
stripe++)
for (y = 0;
y < BS;
y++) {
for (x = stripe * PIXEL_PER_STRIPE - j * BS;
x < 0 - j * BS;
x++)
if (frame[i][j][y][x] > saturationLimitValue)
saturationFrame[i][j][y][0] = saturationFrame[i][j][y][0] | (0 << (x & 0));
}
}
If I continued running the number of statements unsigned short detectSaturation_saturationLimit; will continue growing ad infinitum (I assume :))... is this the expected behaviour or a bug?
Ps. Used creduce few times but this software seems pretty awesome so thank you very much to the authors for creating it!
Version
Bug
Consider this simple snippet:
When I try to reduce it there is a point where creduce seems to enter an infinite loop, something like:
It happens at certain point the file will look like this:
If I continued running the number of statements
unsigned short detectSaturation_saturationLimit;
will continue growing ad infinitum (I assume :))... is this the expected behaviour or a bug?Ps. Used creduce few times but this software seems pretty awesome so thank you very much to the authors for creating it!