search for: core32

I got a qemu crash and errors reported in bochs while trying to get latest core32 branch working (pxelinux): qemu: fatal: Trying to execute code outside RAM or ROM at 0xe6e8aa07 EAX=6e0c7811 EBX=000034b3 ECX=ca68b338 EDX=00000048 ESI=750e3fff EDI=00000020 EBP=d07e4988 ESP=00102324 EIP=e6e8aa07 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0028 00000000 ffffffff 00cf9...

liu asked me for some clarification on how intermode calls work on the core32 branch, so I decided that that was probably something that really should be published more widely. This is the *current state* of the core32 branch; all this stuff is subject to change as development progresses: *** Call from real mode (16-bit) to protected mode (32-bit): These calls are done w...

Well, there is now a development branch in the git repository, which contains the infrastructure needed for rewriting the core in C. As an initial test case it simply contains a "Hello, World!" and a rewrite of rllpack in C. This is not production code in any way: SYSLINUX (the FAT version) is completely broken (I haven't had time to fix the installers yet) and the Linux kernel

...ample, the following instruction converts a double to a single. The source operand is a register of class "Pair64". Is there a way to define it such that the register class is defined at runtime when we know if it should be a 64-bit register class? def FD2S_rr: RRX<0b00110,0,0,0, (outs Core32:$a), (ins Pair64:$b), "FD2S\t$a,$b"),[(set f32:$a, (fpround f64:$b))]>; Example register classes: def Core32: RegisterClass<"XYZ", [i32,f32], 32, (add R0,R1,R2,R3,... def Pair64: RegisterClass<"XYZ", [i64,f64], 64,......