SynthMaker

minor: 1.1.2 fadd sseVar[channel]; crash

Archive · 2008 6 old posts

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

infuzion ·

I was trying to optimize some ASM, & added a fadd input[0]; The fadd colored, but nothing after would. When I connected a CPU Cycle Analyser v1.5 to it, SM crashed & generated a report. I assumed that it would work since the Intel docs list FADD m32fp, Add m32fp to ST(0) and store result in ST(0).

which made me assume that fadd could take an argument. More details & files to be emailed.

While you're in the ASM-Code area, how about adding a few more commands there please? Would make a nice Christmas present 😇

Workaround: Use the stack only. Thanks MyCo!

TomC ·

infuzion wrote: I was trying to optimize some ASM, & added a fadd input[0]; The fadd colored, but nothing after would. When I connected a CPU Cycle Analyser v1.5 to it, SM crashed & generated a report. I assumed that it would work since the Intel docs list FADD m32fp, Add m32fp to ST(0) and store result in ST(0).

which made me assume that fadd could take an argument. More details & files to be emailed.

While you're in the ASM-Code area, how about adding a few more commands there please? Would make a nice Christmas present 😇

I'm nowhere near a SM box right now to verify this, but I'm pretty sure that's one of the SSE commands SM does not support.

Tom

infuzion ·

TomC wrote: ...but I'm pretty sure that's one of the SSE commands SM does not support.

Look inside the Stream Power 😉 But, it seems it will not accept arguments in SM?

MyCo ·

@tomc: fadd is not a sse command, it's a simple FPU command

@infuzion: have you pushed something on the FPU stack before you add?

EDIT: only works without parameters like this:

streamin a; streamin b; streamout c;

fld a[0];fld b[0];fadd;fstp c[0]; fld a[1];fld b[1];fadd;fstp c[1]; fld a[2];fld b[2];fadd;fstp c[2]; fld a[3];fld b[3];fadd;fstp c[3];

infuzion ·

As MyCo said, this error is avoidable. Still shouldn't crash all SM though, & could use more clear documentation, so I'm leaving the bug open, but downgraded to minor.

infuzion ·

Malc reviewed Intel's opcode docs, & determined that SM's fadd actually points to faddp.

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.