>> Moreover, they can be easily cross-generated. If we have proper a >> "src64/sys/x86-64.openBsd.code.l" and "src64/sys/x86-64.openBsd.defs.l" > > To generate the "src64/sys/*.defs.l" files, I always used the attached > "def.c". If you like, you could compile it on OpenBSD, and send me the > output. I could make "src64/sys/x86-64.openBsd.defs.l" then.
Hi Alex, Sorry to get back so late on this... Anyway, I had to make small modifications to get def.c to compile on OpenBSD... i.e +#include <netinet/in.h> -#include <termio.h> Okay, here's the output on amd64 attached to email. Do you need ppc64 too after amd64 works? I can ask somebody on porting list to give me the output for ppc64. They are a friendly bunch when in the right mood. > For the "src64/sys/*.code.l" files, things are a bit more tricky. I > usually worte short test programs in C, and then inspected them with > 'objdump -S'. I don't know how this works out in OpenBSD. Will you please send the test programs? OpenBSD uses gcc 4.2.1 toolchain with binutils 2.15 (moving to binutils 2.17 in this release cycle), so it uses objdump too! Thanks for your help!
def.c.out
Description: Binary data
