High stack in BASOP for IVAS formats

Below is a comparison of stack and heap memory consumption between FLP and BASOP frameworks for EVS mono and IVAS stereo formats. It can be seen that, in particular, the heap is high in both the encoder and decoder in BASOP stereo wrt. BASOP FLP.

		stack [kbytes]		heap [kbytes]
		enc	dec	enc	dec
EVS mono	FLP	98.70	115.09	162.03	198.75
	BASOP	70.94	74.16	138.10	174.12
	BASOP / FLP factor	0.72	0.64	0.85	0.88
IVAS stereo	FLP	164.27	123.57	251.65	305.70
	BASOP	228.82	157.50	224.20	280.69
	BASOP / FLP factor	1.39	1.27	0.89	0.92

Note:

• The numbers are copied from daily automatic tests from January 22, 2026, and EVS mono corresponds to the "StereoDmxEVS, Stereo in, Mono out" case.

The main cause is a duplication of signal buffers in the core-encoder, respectively code-decoder, where typically a float buffer in FLP is often represented in BASOP by two buffers, one in Word16 and another in Word32.

It looks to me that some of these duplicated BASOP buffers can be removed or moved outside the worst-case path.