14:06:10ebrascawhy you need (= *cpu-mode* 64) in modrm-single and jmp?
14:06:11froggeyyes, indirect jmps/calls must use the right register size depending on the cpu mode. separate from that, 64-bit instructions in general are only enabled when assembling 64-bit code
14:12:30ebrascaI can read "if (64-bit mode)" in POWER9 documentation , branch conditional B-form
14:13:50froggeythis is 100% specific to x86 and doesn't apply to POWER
14:41:38froggeyreplacing the quoted bit with whatever code you want to assemble
14:45:06froggeyalternatively you could connect slime to a running mezzano instance and develop through that instead of using sbcl
14:48:56ebrascaI don't have runing mezzano on POWER9.
14:49:31ebrasca(cold-generator:set-up-cross-compiler) give error
14:49:49froggeyyou don't need it running on POWER9, all the assemblers are available on all the architectures
14:49:49ebrascaerror opening #P"/home/ebrasca/system/basic-macros.lisp": No existe el fichero o el directorio
14:50:51froggeythe current directory needs to be the mezzano source directory. (setf *default-pathname-defaults* #p"/path/to/Mezzano/"), with the trailing /
14:53:49ebrascanow (cold-generator:set-up-cross-compiler) give
14:57:01ebrascanow , how to make some starting point for POWER9?
14:59:07froggeypick some instruction to assemble and try to assemble it
14:59:50froggeymodify assemble-lap to call the right function for :power9, create a file for the assembler & add it to the .asd, create a mezzano.lap.power9 package in compiler/cross.lisp
15:01:32ebrascawhy mezzano.lap.power9 and not mezzano.lap.ppc or mezzano.lap.ppc64?
15:18:35froggeyperform-assembly takes a hash-table that maps from instruction symbols to assemblers. the existing assemblers define define-instruction and add-instruction to populate their hash tables
15:43:15ebrascawhere I need to define :sys.lap-ppc64 ?
15:43:42ebrascaI can't find .asd with someting like sys.lap-*