Hey,
I am currently trying to debug a program, where the image map acid builds is
pretty much fubar. This obviously breaks a lot of stuff in acid. Still it
makes me wondering about some design decissions.
eg. asm from port.
It takes it's instructions from symmap. Why? I am interested at the
_curr
> However replacing @addr++ with *addr++ reveils another interesting thing.
> The increment operation searches for the instruction length in the symmap by
> default.
the symbol table has nothing to do with it. the behavior
of ++ depends on the type of addr. in your case, it has
type \I. \I int
int
fmtsize(Value *v)
{
int ret;
switch(v->store.fmt) {
default:
return fsize[(unsigned char)v->store.fmt];
case 'i':
case 'I':
if(v->type != TINT || mach == 0)
error("no size for i fmt pointer ++/--");
Plan9s acid actually does it right.
I consider this a bug in p9ps acid.
--
Andre
i've had a core i7 machine for some time with 4c/8t.
unfortunately, the mp table has only 4 processor entries.
evidently this is also the case on core i5/xeon 3 machines
with >= 4t as well.
in my case, i was given a lucky break by bios which gave
the processors apic ids 0, 2, 4, 6 and the ioap
instead of adding all sorts of goo to the interface,
why not just make the ctl write guarantee
that from the time it returns, the relevant proc
will only run on the wired mach?
russ
