From: Sir Guenther <lists.guenther@googlemail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] acid. cormap vs. symmap
Date: Sun, 4 Apr 2010 21:03:32 +0000 [thread overview]
Message-ID: <u2o27f4bb321004041403r9a0e11a1u406c8e8be4b2fe@mail.gmail.com> (raw)
In-Reply-To: <1720fe559fc2273e7dcbaa798c6f5d7a@ladd.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
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 ++/--");
ret = (*mach->instsize)(symmap, v->store.u.ival);
if(ret < 0) {
ret = (*mach->instsize)(symmap, v->store.u.ival);
if(ret < 0)
error("%r");
}
return ret;
}
}
---
it's always using symmap. replacing it with cormap fixed my problems.
Andre
[-- Attachment #2: Type: text/html, Size: 885 bytes --]
next prev parent reply other threads:[~2010-04-04 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 20:10 Sir Guenther
2010-04-04 20:55 ` erik quanstrom
2010-04-04 21:03 ` Sir Guenther [this message]
2010-04-04 21:19 ` Sir Guenther
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u2o27f4bb321004041403r9a0e11a1u406c8e8be4b2fe@mail.gmail.com \
--to=lists.guenther@googlemail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).