Date: Sun, 4 Sep 2011 13:06:59 +0100 From: Bob Eager <rde@tavi.co.uk> To: freebsd-ports@freebsd.org Subject: Re: [ANNOUNCE]: clang compiling ports, take 2 Message-ID: <20110904130659.7a94cce8@raksha.tavi.co.uk> In-Reply-To: <4E63516B.7000805@FreeBSD.org> References: <20110725155920.GA83490@freebsd.org> <4E631DBF.9000106@yandex.ru> <20110904101252.526de5ef@nonamehost.> <4E632A09.8060904@FreeBSD.org> <20110904114550.71c63078@nonamehost.> <4E63516B.7000805@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 04 Sep 2011 12:22:35 +0200 Matthias Andree <mandree@FreeBSD.org> wrote: > Am 04.09.2011 10:45, schrieb Ivan Klymenko: > > =D0=92 Sun, 04 Sep 2011 09:34:33 +0200 > > Matthias Andree <mandree@FreeBSD.org> =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >=20 > >> Am 04.09.2011 09:12, schrieb Ivan Klymenko: > >> > >>> Maybe this will help: > >>> *rdup_entry =3D *rdup_entry; > >> > >> This is just guessing and probably triggers the same warning unless > >> it's volatile. > >> > >> Have the original author look at it. > >=20 > > This is not guesswork. >=20 > It is DANGEROUS guesswork. Assigning stuff to itself is pointless, so > this is a code bug. >=20 > The only valid exception I know is if you're writing back data to a > command register in a peripheral device, which isn't the case here. >=20 > Fix the bug, not the symptom! I agree, but I can think of another valid exception. System with Hamming correction on the memory, gets a single bit (correctable) error. Need to rewrite the memory contents to reset all the parity bits! (sorry for the drift...)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110904130659.7a94cce8>