search for: fff8

...o the root of the destination device but not to the destination directory (they are copied to the root of the device, but the second copy/move from there to the specified directory may or may not be completed). For example, in one of my attempts I received: Invalid Opcode at 11B1 89CF 0246 BA06 FFF8 0000 0000 0000 0000 1194 0000 0000 0000 and the system hangs. Whatever happens during the installation, when I tried to boot with the destination device, the boot failed to complete (so it seems the boot sector was not written by SYSLINUX.COM). I don't know if this situation was specific...

...he lacing values seem to indicate where the packet boundaries for the two of these are, is this required, or is this just a hint? Further, I'm seeing that the lacing values for audio packets are rather wild. A hex string looks like: 9D 9893 FFFF 08FF FF15 5352 514E 5595 8F92 FFFF 1BFF FF11 FFF8 FF Thats a set of lacing values for one page. Is this also giving me hints (or perhaps an absolute) as to where to find packet boundaries? Thanks - Christopher

I noticed that LLD doesn’t preserve the symbol type for a defsym directive. For example: $ cat f.c void f() {} $ clang -c f.c $ ld.lld -shared --defsym=g=f f.o $ objdump -T a.out DYNAMIC SYMBOL TABLE: 00000000000012a0 g DF .text 0000000000000006 f 00000000000012a0 g D .text 0000000000000000 g f is marked as a function symbol, but g is not. I recognize this is hard to do in the general

Hi all, I have just started playing with speex, and come up with the following code, which just encode a frame of 160 shorts, and the decode it. For some reason the decoded sample is completely different than the original one. is my code wrong? If so what? Or is it a reasonable which depends of values that weren't correctly set? Thanks, Andre #include <stdio.h> #include

...;'vm'', [''name'', ''CentOS_48_64_92''], [''memory'', ''8192''], [''maxmem'', ''8192''], [''vcpus'', ''1''], [''uuid'', ''cc0ef9fb-95e4-fff8-4ce6-2a0d0473a3e7''], [''on_poweroff'', ''destroy''], [''on_reboot'', ''destroy''], [''on_crash'', ''destroy''], [''distro'', ''centos''], [''image'...

I know it's really early in the project's life, but another question I had: How does the generated 68K code perform, at least compared to modern GCC? -- Chris