From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <1ebc06ba0079a91546444a93ab21bc65@quintile.net> <12706eb9d1aafea3af76c427a31aae1a@coraid.com> <20131127203458.7E631B82A@mail.bitblocks.com> Date: Wed, 27 Nov 2013 21:42:27 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=e89a8f234b552d8ba404ec2f7960 Subject: Re: [9fans] compiler bug? Topicbox-Message-UUID: 8c928e62-ead8-11e9-9d60-3106f5b1d025 --e89a8f234b552d8ba404ec2f7960 Content-Type: text/plain; charset=UTF-8 On 27 November 2013 21:35, erik quanstrom wrote: > in the example, don't all the bytes of i correspond to a byte to u, > and thus can't take on unspecified values? > you're right, I was using an overly strict meaning of "correspond" --e89a8f234b552d8ba404ec2f7960 Content-Type: text/html; charset=UTF-8

On 27 November 2013 21:35, erik quanstrom <quanstro@labs.coraid.com> wrote:
in the example, don't all the bytes of i correspond to a byte to u,
and thus can't take on unspecified values?

you're right, I was using an overly strict meaning of "correspond"
--e89a8f234b552d8ba404ec2f7960--