On 04.06.20 12:44, Philipp Klaus Krause wrote:
> The barrier works the other way around: if a replace restart rule has
> been applied, the restart is done at the next barrier rathere than at
> the end of the peephole file.
> But the restart will still start processing from the first rule.
Oh, I supposed it goes from barrier to barrier.
On 04.06.20 12:49, Philipp Klaus Krause wrote:
The z80 (and related) backend currently does not support flags in
notUsed (but the stm8 backend has support for the individual flags c, z,
n in notUsed()).
I’m thinking a few step ahead there.
I plan to implement notUsed('sp'), notUsed('f'), notUsed('af'),
notUsed('zf'), notUsed('nf'), notUsed('hf') and notUsed('cf'), but for
gbz80 only.
I think I can implement notUsed('sp') for z80, too. I can’t implement
flag support for z80, but I’ll try to write it so that it can easily be
extended to other ports.
I have documentation for gbz80 that tells which flags get read and set,
but not for the other ports.
--
Freundliche Grüße / Yours sincerely
Sebastian Riedel
_______________________________________________
Sdcc-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sdcc-user
