From: Graydon Hoare <graydon@redhat.com>
To: binutils@sources.redhat.com
Cc: cgen@sources.redhat.com
Subject: closing and re-opening CPUs in opcodes
Date: Wed, 01 May 2002 15:17:00 -0000 [thread overview]
Message-ID: <20020501181729.D1999@tomago.toronto.redhat.com> (raw)
hm. stress-induced brain seisure, please ignore previous message.
the function in question of course doesn't *receive* a handle,
and must go find one by other means, so naturally it caches it in
a static.
not that this fixes much, but it does explain it. I'll work out a
fix on my own though. never mind.
-graydon
next reply other threads:[~2002-05-01 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 15:17 Graydon Hoare [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-01 15:12 Graydon Hoare
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=20020501181729.D1999@tomago.toronto.redhat.com \
--to=graydon@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=cgen@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).