ChanServ changed the topic of ##yamahasynths to: Channel dedicated to questions and discussion of Yamaha FM Synthesizer internals and corresponding REing. Discussion of synthesis methods similar to the Yamaha line of chips, Sound Blasters + clones, PCM chips like RF5C68, and CD theory of operation are also on-topic. Channel logs: https://freenode.irclog.whitequark.org/~h~yamahasynths
Xyz39808 has quit [Read error: Connection reset by peer]
Xyz_39808 has joined ##yamahasynths
l_oliveira has quit [Quit: ChatZilla 0.9.92-rdmsoft [XULRunner 35.0.1/20150122214805]]
<superctr_>
andlabs, it's a toolchain with two compilers, one of which is sdcc, which is supposed to replace the existing one because it's better
<superctr_>
and yet sdcc still doesn't use ix/iy properly
<superctr_>
so the old one definitely didn't generate good code either
<andlabs>
huh.
<andlabs>
ok.
<andlabs>
why can't people
<ValleyBell>
well... maybe not using ix/iy is a good idea, because using them is so slooooooow
Stilett0 has quit [Quit: leaving]
Patater has quit [Remote host closed the connection]
Patater has joined ##yamahasynths
Stilett0 has joined ##yamahasynths
<superctr_>
depends on what you use them for
<superctr_>
for example, in a sound driver you have a struct with memory for each channel. it makes sense to store the struct address in one of them when dealing with a channel, rather than having to constantly having to calculate the index for some variable
<superctr_>
sdcc likes to use it to just access memory, like doing ld a,(ix+0) instead of ld a,(hl)
<superctr_>
the worst is when sdcc creates a stack frame for local variables
<superctr_>
in which case it will in fact use ix/iy to address variables in that stack frame
ejs__ has joined ##yamahasynths
ej5 has quit [Ping timeout: 256 seconds]
<superctr_>
another thing that sdcc does not do, is to use the af', bc', de', hl' pairs. On the other hand that means you're free to use them in your inline ASM code