pointer <-> integer conversion warnings (bogus -Wall warnings )

[Robert Dewar]

<<No, that is not especially relevant.  The question is whether a
single, ordinary cast ought to be sufficient to mark the legal,
non-portable construct as "intentional", and thus not worthy (under
some combination of options) of warning.
>>

When you write a non-portable construct, you may indeed want to silence
the warning, but only on the target for which you know it works. It seems
just fine to me that when you attempt to port this non-portable construct
to another system, a warning may appear. That forces consideration of whether
the construct still works on the new target.

I really see as very weak the argument that there should be a portable way
of silencing warnings about non-portable constructs.