On 29/05/2010 11:55, Richard Guenther wrote:
> On Sat, May 29, 2010 at 3:16 AM, Dave Korn <dave.korn.cyg...@gmail.com> wrote:
>> What it really is is, I don't see the consistency in disregarding an
>> explicit cast to void, yet permitting a workaround such as an inlined no-op
>> function that casts the parameter to void. Isn't that just a bug, that it
>> fools the warning, and it ought to be fixed?
>
> Yes. Please file a bugreport (and first check the proposed workaround
> really works..).
It does. PR44321.
cheers,
DaveK
