On Sun, 04 Sep 2011 12:22:35 +0200 Matthias Andree <mand...@freebsd.org> wrote:
> Am 04.09.2011 10:45, schrieb Ivan Klymenko: > > В Sun, 04 Sep 2011 09:34:33 +0200 > > Matthias Andree <mand...@freebsd.org> пишет: > > > >> Am 04.09.2011 09:12, schrieb Ivan Klymenko: > >> > >>> Maybe this will help: > >>> *rdup_entry = *rdup_entry; > >> > >> This is just guessing and probably triggers the same warning unless > >> it's volatile. > >> > >> Have the original author look at it. > > > > This is not guesswork. > > It is DANGEROUS guesswork. Assigning stuff to itself is pointless, so > this is a code bug. > > 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. > > 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...) _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"