Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

192 Excellent

About SebRmv

  • Rank
  • Birthday 01/28/1978

Contact / Social Media

Profile Information

  • Gender
  • Location
    Paris, France

Recent Profile Visitors

10,026 profile views
  1. Use the Makefile to build... make build and make run (you have also make help )
  2. You can use that by enabling WSL2 extensions. I tried it with ubuntu on WSL2 and it worked (well, except jcp, but you can use native windows jcp)
  3. Thanks! Actually, since this is my first Python program, there may be some bugs. So if you notice regression, please tell me.
  4. Finally got time to work a bit on the Jaguar Image Converter in Python. This should work reasonably well now. I have not ported all the options that were in the ocaml version (dithering/rotation/cut/...) I'd be happy to get feedback on it (as well as on the Docker environment). Cheers Seb
  5. LOL And thanks, now I can assemble AW
  6. Where should I report bugs? ;;; address register = base of var array VARREG equ 2 .macro emitInstr ;; \1 = instruction move.w \1,(a1)+ .endm .macro emitTgtMem ;; \1 = opcode ;; \2 = variable number (will be multiplied by 2) ;; \3 = address register number add.w \2,\2 beq.s .opt\~ emitInstr #(\1)|(%101<<6)|((\3)<<9) bra.s .done\~ .opt\~: emitInstr #(\1)|(%010<<6)|((\3)<<9) .done\~: .endm ;; emit "move.w #YYyy,xx(Var)" emitTgtMem (%0011<<12)|(%111100),d0,VARREG This one produces a segmentation fault.
  7. Hey, thanks! Also to mention I am working on building a docker environment (based on archlinux) that configures everything. It is ongoing work but this works reasonably well, even on WSL2 (I still need to adapt to use rmac instead of madmac) Repo is here: https://github.com/theRemovers/jagdev I am also working on translating my Jaguar Image Converter in Python, because it is too difficult to maintain the build with ocamlimages.
  8. Yes, with the patch to rmac, no need to modify rmvlib
  9. @ggnI think it is time that I use a more modern tool than MadMac I will report issues if I found any, be reassured It would be great if the patch is integrated to rmac github repo. By doing so, I will be able to officially switch to rmac all my projects.
  10. I applied the patch and it seems to work! Thanks I need to test, test and test now
  11. Ok, many thanks! Will try that edit: just tried, display.s still fails to be assembled (not tried the other files, but I guess it's the same issue)
  12. I think one problem in my code is the use of '*' to refer to current PC, as for instance in the following code: .org G_RAM padding_nop (G_RAM+$10-*) where padding_nop is a macro defined as follows: .macro padding_nop .print "adding ",\1/2," padding nop" .rept (\1 / 2) nop .endr .endm What should I use instead of '*' ?
  13. Hello, I am trying to switch to rmac for building The Removers Library. I get the following errors when compiling display.s: display.s 192: Error: illegal relative address display.s 192: Error: mis-nested .endr First, I believe the line numbers are wrongly reported, because on line 192 stands a local label definition: .gpu_display_from_cpu_it: Secondly, the second error message seems to indicate a problem with a rept/endr. Is there a way to adapt code that was accepted by MadMac? How can I track more precisely the origin of the error? Many thanks! Seb
  14. Thank you so much for your detailed answer I need to read and digest this now
  • Create New...