Brian Kirkbride

I've tried to reduce a problem I'm encountering to a minimal case. The code below, when entered in a codebox

myfunc(a, b, c, d) {
	if (a > 0) {
		a = a - 1;
	}
	if (a <= 0) {
		c = mstosamps(d);
		a = b;
	}
	return a, c;
}

Param bar(4,min=1);
History foo(0);
History baz(0);
foo, baz = myfunc(foo, bar, baz, in1);
out1 = baz;

is being compiled into this, not equivalent code, in the "C" panel on the right:

myfunc(a, b, c, d) {
	if(b > 0) {
		b = b - 1;
	}
	if(b <= 0) {
		c = mstosamps(d);
		b = b;
	}
	return b, c;
}

Param bar(4, min=1);
History foo(0);
History baz(0);
foo, baz = myfunc(foo, bar, baz, in1);
expr_1 = baz;
out1 = expr_1;

Note in particular the replacement of variable "a" with "b" in the generated code.

I'll also say that I've been running into gen~ problems in...well...general. Like a lack of error messages of any kind, but code output that is basically just "expr_1 = in1; out1 = expr_1;" until I correct the error by changing the code around.

Many thanks for pointing out where I'm going wrong or helping to track down a bug.

Hello,

I've tried to reduce a problem I'm encountering to a minimal case. The code below, when entered in a codebox

myfunc(a, b, c, d)...

strange-compilation-results

Following up here to say that I'm encountering more and more incorrect codebox compilations. This is with Version 8.6.2 (d076223e34e) (arm64 mac) BTW.

If I can reduce to simple test cases, I'll post them. But I can summarize that code like

_l1 = 0;
_fade1 = 1;
_l2 = 0;
_fade2 = 1;

// ...

if (some_condition...) {
  _l2 = peek(some_buffer_location...);
  _fade2 = some_calculation...;
}

_out1 = _l1 * _fade1;
_out3 = _l2 * _fade2;

// ...

out1 = _out1;
out3 = _out3;

generates output that doesn't contain the variables or logic above, like

_l1 = 0;
_fade1 = 1;
_out1 = _l1 * _fade1;
expr_123 = _out1;
out1 = expr_123;

Almost like over-optimizing during compilation.

Strange compilation results