On 10/30, Dario Sanfilippo wrote:
>
> > > In
> > > that case; functions such as ba.time would also get an improvement.
> >
> > Why do you think so??
> >
> > perhaps you meant that ba.time can overflow? Yes it can, but I don't
> > think this should depend on -double.
So what exactly did you mean?
On Mon, 30 Oct 2023 at 01:21, Oleg Nesterov wrote:
> Dario, I don't understand you, so let me ask...
>
> On 10/30, Dario Sanfilippo wrote:
> >
> > Perhaps we can include that "^" (pow()) can also be both int or float
> > depending on the operands.
>
> but it already depends on the type of
Dario, I don't understand you, so let me ask...
On 10/30, Dario Sanfilippo wrote:
>
> Perhaps we can include that "^" (pow()) can also be both int or float
> depending on the operands.
but it already depends on the type of operands ?
> perhaps to do everything in
> double when using -double,
On Sun, 29 Oct 2023 at 19:25, Stéphane Letz wrote:
> 1) https://faustdoc.grame.fr/manual/syntax/#numbers is quite clear AFAICS:
>
> ==
> Numbers
>
> Faust considers two types of numbers: integers and floats. Integers are
> implemented as signed 32-bits integers, and floats are implemented
1) https://faustdoc.grame.fr/manual/syntax/#numbers is quite clear AFAICS:
==
Numbers
Faust considers two types of numbers: integers and floats. Integers are
implemented as signed 32-bits integers, and floats are implemented either with
a simple, double, or extended precision depending of
Hi, Oleg.
On Sun, 29 Oct 2023 at 17:02, Oleg Nesterov wrote:
> On 10/29, Dario Sanfilippo wrote:
> >
> > internal int representation is always 32-bit, and Stéphane explained that
> > it can't be changed easily.
>
> Yes, and this is a bit unfortunate
>
> > Since Faust is a high-level language
On 10/29, Dario Sanfilippo wrote:
>
> internal int representation is always 32-bit, and Stéphane explained that
> it can't be changed easily.
Yes, and this is a bit unfortunate
> Since Faust is a high-level language for DSP, wouldn't it make sense to
> treat all signals as float unless there's
Hi, list.
There's a problem when using ints in double-precision; particularly, the
internal int representation is always 32-bit, and Stéphane explained that
it can't be changed easily.
So when compiling with -double,
process = _ * 2^32;
resolves to
virtual void compute(int count, FAUSTFLOAT**
