Veltas/zenv

Issues

• Optimization of "NEXT"

  #23 opened 3 months ago by redirectme
  0

• Optimizing zero_equals

  #22 opened 3 months ago by redirectme
  0

• Some optimization with "EX DE, HL \ JP next"

  #21 opened 3 months ago by redirectme
  0

• Small optimization of COMPARE

  #20 opened a year ago by redirectme
  0

• Optimize "2OVER" with "2@"

  #19 opened a year ago by redirectme
  0

• Using EX (SP), HL in "does_code:", "constant_code:", "execute:", "um_slash_mod:"

  #18 opened a year ago by redirectme
  0

• Replace "create_code" with "swap"

  #17 opened a year ago by redirectme
  1

• Optimize "DU<" with "U<"

  #16 opened a year ago by redirectme
  1

• Remove "CALL colon_code" and "DX exit" from words that do not return control

  #8 opened a year ago by redirectme
  1

• Replace "POP HL \ JP next" to "JP pop_tos_next"

  #7 opened a year ago by redirectme
  2

• Stack pointer moving: use low byte increment instead increment of word if stack is aligned

  #6 opened a year ago by redirectme
  2

• Another register allocation

  #5 opened a year ago by redirectme
  7

• Macro for asm-code inline

  #4 opened a year ago by redirectme
  5

• Add 16K build mode

  #15 opened 2 years ago by Veltas
  0

• Doubles aren't compiled properly

  #14 opened 2 years ago by Veltas
  1

• Compile `TRUE` instead of `-1` in `LITERAL`

  #13 opened 2 years ago by Veltas
  0

• Scroll one line at a time

  #12 opened 2 years ago by Veltas
  0

• `256. 256 256 UM*/` gives `4294967295.`

  #11 opened 2 years ago by Veltas
  1

• `<const> ?` just says `ok` if `?` is undefined

  #9 opened 2 years ago by Veltas
  0

• `-1 du.` shows `8#u94941495`

  #10 opened 2 years ago by Veltas
  1

• Small bug in control.asm: wrong label "j:". It must be "_j:".

  #3 opened 3 years ago by redirectme
  2