linux-kernel - Re: [PATCH] SPI: improve sysfs compiler complaint handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 12 Oct 2006 11:08:59 -0700
From:	David Brownell <david-b@...bell.net>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	dbrownell@...rs.sourceforge.net, Andrew Morton <akpm@...l.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] SPI: improve sysfs compiler complaint handling

On Wednesday 11 October 2006 6:49 pm, Jeff Garzik wrote:

> The compiler complains, even with the "(void)".

> -	(void) device_for_each_child(master->cdev.dev, NULL, __unregister);

Sure seems like a compiler bug to me.  For over two decades, casting
a value into the void has been a standard idiom for saying "ignore
that value" ... ISTR using it to get rid of "unused value" warnings
with LINT on BSD 4.1 systems.

Does anyone know why the GCC folk have decided to go against decades
of common practice here???

- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/