From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] reg DI left allocated
Date: Tue, 15 Oct 2013 22:22:35 +0100 [thread overview]
Message-ID: <CAOw7k5icVTs+tRG5_56CZ81+gdbY3_OEzZ_woUY6QudsTC4EeQ@mail.gmail.com> (raw)
In-Reply-To: <673a1e360037c45cf535458c800e50a5@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 299 bytes --]
On 15 October 2013 20:45, Steve Simon <steve@quintile.net> wrote:
> I assume the answer is just
> to simplify the code
>
Yes, to get it through, but it shouldn't happen. If you can produce a
simplified test case that will be helpful.
It might involve 64-bit ints or structure assignment.
[-- Attachment #2: Type: text/html, Size: 666 bytes --]
prev parent reply other threads:[~2013-10-15 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 19:45 Steve Simon
2013-10-15 19:56 ` erik quanstrom
2013-10-15 21:22 ` Charles Forsyth [this message]
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=CAOw7k5icVTs+tRG5_56CZ81+gdbY3_OEzZ_woUY6QudsTC4EeQ@mail.gmail.com \
--to=charles.forsyth@gmail.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).