From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Tue, 28 Feb 2012 02:20:35 -0500
To: 9fans@9fans.net
Message-ID: <42581047d9bdd824d7f8f43f30636feb@chula.quanstro.net>
In-Reply-To: <CAJQxxw=AN0dUGdu_sbdOc2Vkew3BXWPhvTOAxKKLgjHGxpxVjw@mail.gmail.c>
References: <8f46f79042d0cf94c0309c883a046dd6@brasstown.quanstro.net>
	<CAJQxxw=AN0dUGdu_sbdOc2Vkew3BXWPhvTOAxKKLgjHGxpxVjw@mail.gmail.c>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] 6c bug?
Topicbox-Message-UUID: 64fe5c56-ead7-11e9-9d60-3106f5b1d025

On Tue Feb 28 02:16:04 EST 2012, bruce.ellis@gmail.com wrote:
> what values of p[1] do you expect the test to be of use?
>=20
> On 28 February 2012 15:40, erik quanstrom <quanstro@quanstro.net> wrote=
:
> > for p =3D uchar*, Nbus=3D=3D256,
> >
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0if((uint)p[1] =
>=3D Nbus){
> >
> > generates
> >
> > =C2=A0 =C2=A0 =C2=A0 =C2=A0warning: ./mp.c:212 useless or misleading =
comparison: UCHAR >=3D 0x100
> >
> > i'm pretty sure that 6c is incorrectly issuing the diagnostic before
> > applying the cast. =C2=A0(the cast is there to shut the compiler up.)

it is not a given that Nbus >=3D 255.

- erik