Date: Wed, 17 Mar 2004 23:30:14 +0200 From: Ruslan Ermilov <ru@FreeBSD.org> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: ia64@FreeBSD.org Subject: Re: [current tinderbox] failure on ia64/ia64 Message-ID: <20040317213014.GB46747@ip.net.ua> In-Reply-To: <20040317205104.GA29066@dhcp01.pn.xcllnt.net> References: <20040317040254.386947303A@freebsd-current.sentex.ca> <xzpad2fhixn.fsf@dwp.des.no> <20040317113931.GF49920@ip.net.ua> <20040317200307.GA46126@ip.net.ua> <20040317205104.GA29066@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--gj572EiMnwbLXET9
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Mar 17, 2004 at 12:51:04PM -0800, Marcel Moolenaar wrote:
> On Wed, Mar 17, 2004 at 10:03:07PM +0200, Ruslan Ermilov wrote:
> > > >=20
> > > > for(i =3D 0; i < SOUND_MIXER_NRDEVICES; i++) {
> > > > if ((1 << i) & mask) {
> > > > v |=3D mt[i].iselect;
> > > > }
> > > > }
> > > >=20
> > >=20
> > Actually, this is easily reproduceable by compiling the corresponding
> > module on pluto1 with CFLAGS=3D"-O2 -pipe" set in environment. There's
> > clearly a bug in gcc(1), as:
>=20
> What happens if you replace the for-loop with an equivalent while-loop?
>=20
Doesn't make any difference. sparc64 and amd64 do not exhibit this problem.
(Yes, I tested this on amd64 as well, skipping the final ld(1) step of the
module's build.)
Cheers,
--=20
Ruslan Ermilov
FreeBSD committer
ru@FreeBSD.org
--gj572EiMnwbLXET9
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFAWMNmUkv4P6juNwoRAuwDAJ9vTXLM1PU/x7lxZGaXSTERelgztgCfVhpM
51Jv5/zoqAA3/G/6cyAA4JM=
=sJDW
-----END PGP SIGNATURE-----
--gj572EiMnwbLXET9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040317213014.GB46747>